August 23, 2017 at 8:27 pm
Comments posted to this topic are about the item Executing commands in SQLCMD
August 24, 2017 at 12:43 am
Nice simple question, thanks Steve.
...
August 24, 2017 at 6:10 am
Nice, simple question, thanks Steve....
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
August 24, 2017 at 7:40 am
Thom A - Thursday, August 24, 2017 1:24 AMBad Steve, where was the semicolon?! 😉
Just hadn't typed it yet 😉
August 25, 2017 at 4:53 am
Thanks Steve, it was very informative, like always.
August 25, 2017 at 5:41 am
Steve Jones - SSC Editor - Thursday, August 24, 2017 7:40 AMThom A - Thursday, August 24, 2017 1:24 AMBad Steve, where was the semicolon?! 😉Just hadn't typed it yet 😉
They aren't mandatory yet. At least not yet not in most contexts - only some statements require that the preceding statement be terminated, and GO isn't one of them (in fact it's not even a statement). I wonder when they will be mandatory in the sense that all statements must be terminated by a semicolon (so that, fo example a block has to be terminated by "; END" and if the end of the block is also the end of the statement that will have to be "; END;".)
I susect that the "backwrd compatability" argument that MS regularly uses to avoid fixing various sillinessses in SQL Server will mean that semicolons won't become mandatory terminators for all T-SQL statements during my lifetime.
Tom
August 28, 2017 at 5:31 am
Nice and simple question with a simple answer. Thom, good observation on the semicolon.
August 28, 2017 at 5:40 am
TomThomson - Friday, August 25, 2017 5:41 AMSteve Jones - SSC Editor - Thursday, August 24, 2017 7:40 AMThom A - Thursday, August 24, 2017 1:24 AMBad Steve, where was the semicolon?! 😉Just hadn't typed it yet 😉
They aren't mandatory yet. At least not yet not in most contexts - only some statements require that the preceding statement be terminated, and GO isn't one of them (in fact it's not even a statement). I wonder when they will be mandatory in the sense that all statements must be terminated by a semicolon (so that, fo example a block has to be terminated by "; END" and if the end of the block is also the end of the statement that will have to be "; END;".)
I susect that the "backwrd compatability" argument that MS regularly uses to avoid fixing various sillinessses in SQL Server will mean that semicolons won't become mandatory terminators for all T-SQL statements during my lifetime.
It was deprecated a couple versions ago, but I don't remember when. With the "minimum 2 versions" they could make them mandatory whenever they want. Nonetheless, I think it'll probably be a while.
September 4, 2017 at 2:50 am
Ed Wagner - Monday, August 28, 2017 5:40 AMIt was deprecated a couple versions ago, but I don't remember when. With the "minimum 2 versions" they could make them mandatory whenever they want. Nonetheless, I think it'll probably be a while.
I wouldn't be surprised if it happens in SQL Server 2030 or something silly.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
September 4, 2017 at 7:10 am
Ed Wagner - Monday, August 28, 2017 5:40 AMTomThomson - Friday, August 25, 2017 5:41 AMSteve Jones - SSC Editor - Thursday, August 24, 2017 7:40 AMThom A - Thursday, August 24, 2017 1:24 AMBad Steve, where was the semicolon?! 😉Just hadn't typed it yet 😉
They aren't mandatory yet. At least not yet not in most contexts - only some statements require that the preceding statement be terminated, and GO isn't one of them (in fact it's not even a statement). I wonder when they will be mandatory in the sense that all statements must be terminated by a semicolon (so that, fo example a block has to be terminated by "; END" and if the end of the block is also the end of the statement that will have to be "; END;".)
I susect that the "backwrd compatability" argument that MS regularly uses to avoid fixing various sillinessses in SQL Server will mean that semicolons won't become mandatory terminators for all T-SQL statements during my lifetime.It was deprecated a couple versions ago, but I don't remember when. With the "minimum 2 versions" they could make them mandatory whenever they want. Nonetheless, I think it'll probably be a while.
Heh... especially when most of the MS stored procedures in Master and MSDB don't have it yet.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2017 at 5:26 am
Jeff Moden - Monday, September 4, 2017 7:10 AMEd Wagner - Monday, August 28, 2017 5:40 AMTomThomson - Friday, August 25, 2017 5:41 AMSteve Jones - SSC Editor - Thursday, August 24, 2017 7:40 AMThom A - Thursday, August 24, 2017 1:24 AMBad Steve, where was the semicolon?! 😉Just hadn't typed it yet 😉
They aren't mandatory yet. At least not yet not in most contexts - only some statements require that the preceding statement be terminated, and GO isn't one of them (in fact it's not even a statement). I wonder when they will be mandatory in the sense that all statements must be terminated by a semicolon (so that, fo example a block has to be terminated by "; END" and if the end of the block is also the end of the statement that will have to be "; END;".)
I susect that the "backwrd compatability" argument that MS regularly uses to avoid fixing various sillinessses in SQL Server will mean that semicolons won't become mandatory terminators for all T-SQL statements during my lifetime.It was deprecated a couple versions ago, but I don't remember when. With the "minimum 2 versions" they could make them mandatory whenever they want. Nonetheless, I think it'll probably be a while.
Heh... especially when most of the MS stored procedures in Master and MSDB don't have it yet.
Touche, sir. In fact, I don't know any of them that do...the last time I looked, anyway.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply