Home Forums SQL Server 2012 SQL 2012 - General Impact of trace flag 272 on SQL Server 2012 apart from disabling identity jump RE: Impact of trace flag 272 on SQL Server 2012 apart from disabling identity jump

  • russc-993845 (10/29/2014)


    I understand that the identity value is "meaningless", but in previous version of MSSQL it provided me with an accurate enough incremental number to allow for accurate auditing. In over 5 years, I have millions of e-commerce transactions and have only had 11 identity numbers not be sequential. 5 of them were deletions, so 6 were non-committed transactions. For my use, that was accurate enough and I'm sure there are many other developers who used it the same way.

    You had luck. Sometimes it is unfortunate to have luck, because it may lead to that you become dependent on an inapproriate solution.

    They should provide more documentation on TF272, it's impact, etc. I have even read that it requires a lower case t, though some say it works with upper case.

    There is no lower- or uppercase for digits. 🙂 If you are thinking of the startup option to set the trace flag, this option is documented in Books Online, and it is -T.

    [font="Times New Roman"]Erland Sommarskog, SQL Server MVP, www.sommarskog.se[/font]