February 19, 2013 at 4:25 am
Hi,
Using SQL Row Versioning is there is any possibility to get the history of row data from the updated table.
And also can any one tell me what is difference of Read committed isolation and Snapshot isolation level row version in simple words, 😉
February 19, 2013 at 4:35 am
Row Versioning? You mean adding a timestamp column to the table which changes when rows are updated etc? - No there is no way to know the old data. You could look at using CDC or implimenting triggers but could cause you more problems.
The difference between the two DB level snapshots is that 1 keeps the row version alive until the oldest session no longer needs it, the other keeps it alive until the oldest transaction no longer needs it. IIRC
http://msdn.microsoft.com/en-us/library/ms189050%28v=sql.105%29.aspx
February 19, 2013 at 4:49 am
Thank you very much for you reply....
So which is recommended Row Versioning in sql? how to decide it...?
February 19, 2013 at 4:52 am
You decide if you need row versioning on a table or not, its there to tell you when a row has changed, hence the timestamp hash changes. Its not an audit of what it was to what it is, for that you need CDC or custom auditing.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply