Red Gate forums :: View topic - Data loss
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL Log Rescue
SQL Log Rescue forum

Data loss

Search in SQL Log Rescue forum
Post new topic   Reply to topic
Jump to:  
Author Message
kirkr



Joined: 14 Aug 2006
Posts: 2

PostPosted: Mon Aug 14, 2006 3:50 pm    Post subject: Data loss Reply with quote

SQL Log Rescue Version: 1.1.0.229
DB Recovery Model: Simple
Auto Shrink: On
Issue: a record has been inserted into the table and at a later time deleted. SQL Log Rescue has this transaction however the script does not recover all the data;

* Some date fields that are actually NULL have been returned by SQL Log Rescue as '19000101 00:00:00.000'.
* Some bit fields that are actually zero (0) have been returned as NULL.
* Some nvarchar fields that are actually NULL have been returned as ''.
* Some nvarchar fields that are populated have been returned as ''.

I'm presuming this may be related to the recovery model and data loss but how did that 01/01/1900 date get involved and nulls returned as blanks, etc., could there be an issue with SQL Log Rescue?

Extract of some of the values from an SQL Log Rescue UNDO delete script;

...'19000101 00:00:00.000', NULL, NULL, NULL, NULL, N'13', N'625 (PAL) SD ', N'', NULL, NULL, NULL, '19000101 00:00:00.000', NULL, '19000101 00:00:00.000', NULL,...
Back to top
View user's profile Send private message
Brian Donahue



Joined: 23 Aug 2004
Posts: 6580

PostPosted: Tue Aug 15, 2006 6:44 pm    Post subject: Reply with quote

Hello,

Sorry but we don't have any explanation as to why Log Rescue is behaving like this. It would need to specifically cast the NULL data in the column to DateTime.MinVal, and there isn't any logic in the software doing that. We would probably need to see the dataabse to find the source of the problem.
Back to top
View user's profile Send private message
kirkr



Joined: 14 Aug 2006
Posts: 2

PostPosted: Tue Aug 15, 2006 6:56 pm    Post subject: Reply with quote

I've briefly reviewed since and it is SQL Server that interprets zero (0) as the date 01011900. I believe SQL Log Rescue has moved the data values from one column to the next, of a different data type, thus causing the issue. I'm not sure why as it correctly populated some records but not others. I am presuming SQL Log Rescue has interpreted the data values finding some form of character (or sequence of) in the transaction log and interpreted an additional data value.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group