|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: 2 days ago @ 12:45 PM
Points: 1,117,
Visits: 1,135
|
|
Thanks for the question. I was ticked since I got it wrong, but it is too easy to just gloss over a script when reading it. A good reminder to be careful.
-Dan
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, July 25, 2012 9:04 PM
Points: 542,
Visits: 187
|
|
| I thought ';' is a typo and ignored that.
|
|
|
|
|
SSChasing Mays
      
Group: General Forum Members
Last Login: Sunday, March 04, 2012 4:02 AM
Points: 660,
Visits: 134
|
|
DhruvShah (9/28/2010) I thought ';' is a typo and ignored that.
LOL....
Who uses a ';' anyway? it's not yet standard practice and if you do, you should realise that it would cause problems in the middle of a statement.
I need to buy some glasses now... I thought the trick was with the subquery referencing the main table with an alias, which is more informative. Suppose, I need to buy some glasses now...
|
|
|
|
|
SSCrazy
      
Group: General Forum Members
Last Login: Monday, May 13, 2013 11:21 AM
Points: 2,163,
Visits: 2,148
|
|
terrykzncs (4/22/2011) Who uses a ';' anyway? it's not yet standard practice and if you do, you should realise that it would cause problems in the middle of a statement.
For starters anyone that has to use Oracle. (Since it is required.)
Also, Microsoft has deprecated not using ; so in the next version or two of SQL Server you will probably be required to, so it might be a good idea to start now so you don't have to go back and add the ; to all of your code later.
From http://msdn.microsoft.com/en-us/library/ms143729.aspx:
Not ending Transact-SQL statements with a semicolon.
|
|
|
|