Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jazzcatone
Starting Member
12 Posts |
 Posted - 2010-08-27 : 18:33:20
|
| Trying to roll db forward in SQL ServerQuestion: I am in the middle of testing some SQL Server 2008 backup and restore scenarios. One of the scenarios I am rehearsing for is if I need to investigate for fraud. I would like to restore to a new db. Then I would like to roll transaction logs forward to help to pinpoint when the fraud occurred. So currently I can take the production db and restore it to say 2pm to a new temporary db. I leave this temporary database in STANDBY mode so as to be able to roll it forward with more transaction logs so I am to be able to investigate when the fraud occured.However, in SQL Server 2008 whenever I go to roll the log forward (by choosing tasks--restore-transaction logs..- and picking my logs) I get the follwing error:System.Data.SqlClient.SqlError: The log in this backup set terminates at LSN 1536000000408300001, which is too early to apply to the database. A more recent log backup that includes LSN 1537000000642400001 can be restored. (Microsoft.SqlServer.Smo)I am confused. If I understand this its telling me I am trying to restore logs that I don't have to. (Is that correct?) In the sql server gui if I pick a transaction log at say 4pm it automatically puts check marks next to all of the transaction logs listed before that as well. There is something I am not understanding.... if i restore to say 2pm, and I am in STANDBY Mode, and my next log was run at 2:15, should I not just be able to select that one for the next restore?? Or am I just not understanding the process correctly.Any advice would be greatly appreciated.JasonJason |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2010-08-27 : 18:40:41
|
| Yes you are correct. The fact that you are getting that error means that one or more needed transaction logs to get you to the point in time you have selected have either not been checked or have been wiped from the backup history (unlikely). I do my point in time recovery via RESTORE LOG command rather than the GUI that way I know for sure which files I've selected. I don't rely on the GUI as I don't trust it.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
|
|
|
Rolling a SQL Server Database Forward