InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSat, 18 May 2013 21:43:43 GMT20http://www.sqlservercentral.com/Forums/Topic1421542-2799-1.aspxYou 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.Tue, 19 Feb 2013 04:52:12 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1421542-2799-1.aspxThank you very much for you reply....So which is recommended Row Versioning in sql? how to decide it...?Tue, 19 Feb 2013 04:49:05 GMTratheesh4sqlhttp://www.sqlservercentral.com/Forums/Topic1421542-2799-1.aspxRow 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[url]http://msdn.microsoft.com/en-us/library/ms189050%28v=sql.105%29.aspx[/url]Tue, 19 Feb 2013 04:35:20 GMTanthony.greenhttp://www.sqlservercentral.com/Forums/Topic1421542-2799-1.aspxHi,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, ;-)Tue, 19 Feb 2013 04:25:53 GMTratheesh4sql