Erland,

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.

This might not be the "perfect" solution, but for me is was simple and accurate enough for what I needed. MS changes have a big impact on my application. 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.