Introduction to SQL Server 2005

  • Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/fFinney/introductiontosqlserver2005.asp

  • Interesting article!

    Is it fair to say that the new SQL keywords , like NTile, and RANK, are more geared towards statistical analysis of data, rather than just doing simple database operations(like updates, inserts, deletes)?

  • The article is very poorly written, and apparently not even proofread.

  • Excellent Article with a good overview of develoment features.

    I somewhat aggree with Alan too: the examples have typos unless the author did modify his AdventureWorks database.

    In the first example in 3.1.1

    Select row_number() over (order by SalesOrderDate desc) as RowNum,OrderID, CustomerID, SalesOrderDateFrom Sales.OrderHeaderOrder by SalesOrderDate Desc

    Should read:

    Select

    row_number() over (order by OrderDate desc) as RowNum,

    SalesOrderID

    , CustomerID, OrderDate

    From

    Sales.SalesOrderHeader

    Order

    by OrderDate Desc

     

    In the second example in 3.1.2

    State.StateProvinceID

    should read

    StateProv.StateProvinceID

    Since I made a mistake myself trying to point to the mistakes in the second example  I guess it is not the author's fault that the names are complex

    Regards,Yelena Varsha

  • Is the MERGE INTO .. there at all in the released version???

    I searched the whole Books Online, it's nowhere to be found. Besides I tried executing the example given for this it fails.   


    bm21

  • Thanks for the article..  I don't normally try out the code samples so for me the article was great   Didn't know about merge into - will avoid a lot of the if exists(select * from ....) then update... else insert... code in my stored procs!

  • Got very frustrated when the examples were not working. MERGE INTO is no longer supported by SQL 2005. Other than that not a bad article.

  • Great article!  And, I didn't like the Merge Into function anyway...

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Just piping in on a something I just noticed in playing with INTERSECTand EXCEPT.  I expected that they would act identicle to EXISTS and NOT EXISTS but they don't.  They treat nulls differently.

    Based on the author's example create a quick reference table.

    SELECT

    TOP 1000 CustomerID, OrderDate, SalesPersonID

    INTO

    Sales.SalesOrderHeaderIntersection

    FROM

    Sales.SalesOrderHeader

    I expected the following two queries to return the same results.

    SELECT

    CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeader INTERSECT

    SELECT

    CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeaderIntersection

     

    SELECT

    CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeader t1

    WHERE

    EXISTS

    (

    SELECT * FROM Sales.SalesOrderHeaderIntersection t2 WHERE t1.CustomerID=t2.CustomerID

    AND t1.OrderDate=t2.OrderDate AND t1.SalesPersonID=t2.SalesPersonID)

    They do not because [NOT] EXISTS ommitts the nulls as a non match while INTERSECT includes them

  • Good Article,However would like to see more articles coming with focus on DBA aspects!

    Cheers,

    Raghu Pyapili

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply