25112
asked on
new identity feature in 2012 with cache- overcoming the cons of it.
with the new 'jump identity value' feature in SQL 2012,
one SQL MVP says
"If you need contiguous numbers, you should not use neither IDENTITY nor sequences"
https://social.technet.microsoft.com/Forums/sqlserver/en-US/bd8fafde-15d9-47aa-8030-ee8f6e48a482/impact-of-trace-flag-272-on-sql-server-2012-apart-from-disabling-identity-jump
there is a Trace fix.. but in one of the user comments i read [This (trace fix) is working for standalone server but not cluster servers.]
http://www.dfarber.com/computer-consulting-blog/2014/2/13/how-to-solve-identity-problem-in-sql-2012.aspx
1)if you do desire contiguous numbers, what options do you have other than SQL Identity or sequences?
2)from what i understand, the trace 272 suppresses the cache feature in sql 2012 for identity column: if high availability feature is turned on or used in 2012, if there is a failover, will the trace be effective in that scenario,?
one SQL MVP says
"If you need contiguous numbers, you should not use neither IDENTITY nor sequences"
https://social.technet.microsoft.com/Forums/sqlserver/en-US/bd8fafde-15d9-47aa-8030-ee8f6e48a482/impact-of-trace-flag-272-on-sql-server-2012-apart-from-disabling-identity-jump
there is a Trace fix.. but in one of the user comments i read [This (trace fix) is working for standalone server but not cluster servers.]
http://www.dfarber.com/computer-consulting-blog/2014/2/13/how-to-solve-identity-problem-in-sql-2012.aspx
1)if you do desire contiguous numbers, what options do you have other than SQL Identity or sequences?
2)from what i understand, the trace 272 suppresses the cache feature in sql 2012 for identity column: if high availability feature is turned on or used in 2012, if there is a failover, will the trace be effective in that scenario,?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for explaining the situation how you are forced to use explicit transactions for financial sequence..
does that mean for the most part ,you are not using identity or sequence feature?
in a sence, sql 2012 takes us backward a little bit on this feature?
there is not *much* complaint over this in the SQL world, is there?