Home Forums SQL Server 2012 SQL 2012 - General Identity key (unique column) not behaving properly RE: Identity key (unique column) not behaving properly

  • March 5, 2015 at 9:21 am

    #1781964

    sql-lover (3/5/2015)

    sqlcentral.dah328 (3/4/2015)

    I ran into this same problem with SQL Server 2012 and this was one of the few places where anyone took seriously the possibility that the identity seed was not being externally reset. In any case, running my application under load would generally result in the problem occurring within an hour. After upgrading to SP2CU4, I could no longer reproduce the problem after 12+ hours of runtime. Perhaps something in CU4 resolved it. I am in the process of testing the application with SQL Server 2014 to see if it has the same behavior.

    Thanks for sharing. I'm still running the trace flag on my 4 Pro boxes, it was my workaround.

    Are you referring to this link ?

    I am not using sequences anywhere in my application, but the description of the sequence bug describes my symptoms exactly. I wonder if SQL Server 2012 uses sequences under the covers to implement integer identity columns. If so, that would explain a lot.