April 12, 2011 at 10:23 am
I know the rowversion increments every times thers inserts/updates but i want to know is there a limit on it. and what is the best way to grab cdc with row version , mean which data type it should change to while comapring and storing.
Thanks..
April 12, 2011 at 2:03 pm
It's an 8-byte number. From BOL:
A nonnullable rowversion column is semantically equivalent to a binary(8) column. A nullable rowversion column is semantically equivalent to a varbinary(8) column.
April 12, 2011 at 2:10 pm
For change control purposes, we usually convert these values to BIGINTs. Easier to pass back and forth from middle tier.
_____________________________________________________________________
- Nate
April 13, 2011 at 11:42 am
Is there Any limit on rowversion...i mean is thee any possibility that Database reached its maximum rowversion?
April 13, 2011 at 11:54 am
kick_12309 (4/13/2011)
Is there Any limit on rowversion...i mean is thee any possibility that Database reached its maximum rowversion?
Sure it's possible.
But, just using BIGINT starting at 1 and doing 5000 changes per second will still take roughly 58494241 years to use them up. Considering rowversion is binary, (which I think to mean unsigned) it would take about twice as long to use them up.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply