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/