Data loss

kirkr

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,...

Brian Donahue

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.

kirkr

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.