Perhaps. I like identities, but last year some of the Data Warehouse guys from MS said the GUID is faster. Identity tops out around 4000/sec?, I think.
The Best of SQL Server Central.com 2002 - http://www.sqlservercentral.com/bestof/
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
Another fine article.
I like the way you state that it's YOUR OPINION that Identity shouldn't be used. And you really didn't say it shouldn't ever be used. You just stated that this is another reason it shouldn't be used; that leaves it open to being used for other reasons.
It would be a good idea to run
DBCC CHECKIDENT (<tablename>, RESEED, 1)
every time before reloading so the identity seed is reset to 1 and you will never reach such a large number even if the table is reloaded millions of times!
Thanks alot for sharing this. I was temporarily baffled when I got this error until I realized that we had set up our ID as a smallint. A quick search on SQL Server Central came to my rescue again.
Viewing 4 posts - 16 through 18 (of 18 total)