January 22, 2009 at 6:38 am
Agreed, Jeff.
Without the business reason for this, it is really hard to understand why a BIGINT IDENTITY column would not fulfill the requirement.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
January 24, 2009 at 1:43 pm
I suppose you could always pad a bigint with a char string using a calculated column. Using rowversion won't technically port across servers and even a database which could give problems in other/test environments or if the server was upgraded or db migrated - afaik rowversion = timestamp and I proved this issue when using timestamps - I wait to be corrected if I'm wrong - as not tested this.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 31 through 31 (of 31 total)
You must be logged in to reply to this topic. Login to reply