July 26, 2004 at 10:06 am
For a certain reason I loose the transaction log file (disk failure), but I have all the data files in good status, on a separate drive. I try to attach them as database to SQL Server and I get the message: "The file name specified for file log isincorrect. A new log file may be created. Do you want to continue?"
If I press the button a new log is created and database seems OK.
However, some data must have been lost, but what is exactly the size of the damage? I would say that all data changed since the last checkpoint and all not committed transaction, but I am not sure.
Can anybody clarify this for me?
Thanks to all that will give me a clue.
Gabriela
July 26, 2004 at 10:27 am
It should be all changes that were not committed. Does this not seem to be the case?
July 26, 2004 at 12:41 pm
First the really good news...you didn't lose the datafiles. That means you recovered all or most of the data.
The log file is used to apply committed changes to a full backup that were not part of the full backup. However, in your case, you have the datafile (.mdf) and didn't need to restore from a full backup. Good.
When the database crashed, all the uncommitted transactions should have been rolled back. So consider that they never happened. Your job now is to figure out which transactions failed. Take the time of the disk failure and go back one hour before that. Notify all your users that any changes/additions they made as of that time may not have made it into the database. Have them check their data and re-enter any missing information. (You may even want to have them go back 2 hours before the crash, but most changes started that early should have been committed by the time of the crash).
-SQLBill
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply