|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Thursday, June 26, 2008 6:11 PM
Points: 1,
Visits: 2
|
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Tuesday, September 28, 2010 7:32 AM
Points: 121,
Visits: 32
|
|
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)?
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Thursday, October 02, 2008 7:37 AM
Points: 19,
Visits: 19
|
|
| The article is very poorly written, and apparently not even proofread.
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Monday, July 30, 2012 10:42 AM
Points: 3,434,
Visits: 519
|
|
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, OrderDateFrom Sales.SalesOrderHeaderOrder 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 Varshal
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, November 23, 2009 4:45 AM
Points: 163,
Visits: 9
|
|
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
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Sunday, September 16, 2012 3:26 AM
Points: 1,038,
Visits: 443
|
|
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!
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Monday, December 17, 2012 3:53 AM
Points: 135,
Visits: 77
|
|
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.
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 1:51 PM
Points: 32,906,
Visits: 26,789
|
|
|
|
|
|
Old Hand
      
Group: General Forum Members
Last Login: Friday, May 03, 2013 9:17 AM
Points: 325,
Visits: 169
|
|
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.SalesOrderHeaderIntersectionFROM Sales.SalesOrderHeaderI expected the following two queries to return the same results. SELECT CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeader INTERSECTSELECT CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeaderIntersection SELECT CustomerID, OrderDate, SalesPersonID FROM Sales.SalesOrderHeader t1WHERE EXISTS( SELECT * FROM Sales.SalesOrderHeaderIntersection t2 WHERE t1.CustomerID=t2.CustomerIDAND 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
|
|
|
|
|
Grasshopper
      
Group: General Forum Members
Last Login: Friday, July 24, 2009 12:57 AM
Points: 21,
Visits: 16
|
|
Good Article,However would like to see more articles coming with focus on DBA aspects! Cheers, Raghu Pyapili
|
|
|
|