|
|
Posted by Erland Sommarskog on 05/25/05 23:20
(mark_drewersback@yahoo.co.uk) writes:
> By screwed, I mean, the app that is running from it is now reporting
> duplicate primary key errors. We have the mdf file. What I'd like to
> know is if we succesfully restored it using the mdf/ldf file then would
> it be possible to roll back to the previous Friday, when it was running
> fine, given that no back ups have taken place?
If there had been been a one-year old backup, and an unbroken transaction
log since then, yes.
If there is no backup at all, I don't think you can do it with the commands
that ships with SQL Server.
However, there are 3rd party tools out there that can read the transaction
log, and generate commands to undo transactions in the transaction log.
Lumigent Log Explorer (www.lumigent.com) has been in business for a long
time. Log Pi (www.logpi.com) is another alternative.
I would suggest that the best to examine more close why you get PK
duplicates.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|