Scripting procedure versions

  • RonKyle - Friday, March 8, 2019 2:24 PM

    Gosh MS really has made this one fun. My version is 12.0.2000.8 and it gets only one. I just used another machine which has 12.0.4100.1 and it returns both versions. I was connected to the same database in both versions of SSMS. There is nothing like consistency and this is certainly nothing like consistency.

    It is deprecated, so I wouldn't expect much.

    I know it is deprecated and not something I would use but seems really strange that the behavior changed after it was deprecated and then the original behavior came back in a later release. Something is a bit fishy there. Probably another case where MS decides to deprecate something yet they use it themselves so they can't really deprecate it and have to go back and maintain it for their code to continue working. Sort of like the text datatype that we all know should be taken out back and shot except that MS has it splattered all over their system procedures.

    _______________________________________________________________

    Need help? Help us help you.

    Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.

    Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.

    Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
    Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
    Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
    Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/

  • Sean Lange - Friday, March 8, 2019 2:52 PM

    RonKyle - Friday, March 8, 2019 2:24 PM

    Gosh MS really has made this one fun. My version is 12.0.2000.8 and it gets only one. I just used another machine which has 12.0.4100.1 and it returns both versions. I was connected to the same database in both versions of SSMS. There is nothing like consistency and this is certainly nothing like consistency.

    It is deprecated, so I wouldn't expect much.

    I know it is deprecated and not something I would use but seems really strange that the behavior changed after it was deprecated and then the original behavior came back in a later release. Something is a bit fishy there. Probably another case where MS decides to deprecate something yet they use it themselves so they can't really deprecate it and have to go back and maintain it for their code to continue working. Sort of like the text datatype that we all know should be taken out back and shot except that MS has it splattered all over their system procedures.

    That is an interesting comment.  Apparently the reason it's being deprecated is that the semi-colon interferes with some new programming.  That could make from some interesting discussions if somehow they've built this in their systems in a way that makes it difficult to remove the feature.

Viewing 2 posts - 16 through 16 (of 16 total)

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