Post reply

predict the output

  • January 2, 2014 at 1:42 am

    #1676805

    Good one. 🙂

  • January 2, 2014 at 2:19 am

    #1676809

    Hugo Kornelis (12/30/2013)

    Probable reasons for this decision:

    1. Maybe the IDENTITY code is not nice modularized, but spread out throughout the other code, and changing it is hard and risky. Too hard and risky.

    2. Maybe MS realized that the intended use of IDENTITY is to generate numbers, and hence decided not to put any effort in influencing which numbers are generated.

    3. Maybe MS found out that, despite what I just wrote above, some important customer actually has code that relies on this behaviour, and they didn't want to tick off this customer by changing it.

    It's probably a combination of at least two of the above.

    I'd guess at (2). It always rings alarm bells with me when someone describes a database in which the actual values of ID columns are of any significance.

  • January 6, 2014 at 3:13 am

    #1677675

    Nice question, thanks.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • January 8, 2014 at 3:10 am

    #1678358

    nice and easy..

    Thanks.

  • March 15, 2014 at 2:23 am

    #1697395

    Easy, but important question! Thanks

    /Håkan Winther
    MCITP:Database Developer 2008
    MCTS: SQL Server 2008, Implementation and Maintenance
    MCSE: Data Platform

Viewing 5 posts - 16 through 19 (of 19 total)

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