Derek Kalweit said:
http://www.red-gate.com/products/sql_log_rescue/index.htm
many thanks to Derek for that, and many ????'s to those who thought it
couldn't be done; said I just needed a restore from the 'usual' set of
backups; or that I should rtfm.
fwiw Derek's suggestion works out of the box, does what it says on the tin,
and is now available free of charge.
I didn't say this was a production database, it's actually pre-production
and we're in data cleansing mode which is why I was in Query analyser
deleting a few bad records when I had 'finger trouble'.
Nor did I say it was done in code, as it happens my standard is to have
void flags in records and not allow the app/ user to delete anything.
Restore from <mode type=smug> your latest backup </mode> - now why would/
should I need to restore from a backup in this situation? (btw there *was*
a backup, if a bit old):
I had just issued a 'bad' delete instruction, restoring from a backup and
rolling forward the log to the point before the f*up would be laborious and
risky, and as Micheal Babcock pointed out would lose any work done after
the f*up and before I disabled the database.
Oracle in this exact situation would allow me to rollback the 'implicit'
transaction (if I was really quick <g>), but not SQL Server.
sql_log_rescue effectively does just that, it extracts everything from the
log (takes a few minutes), allows you to select a command [block] and unDo
it.
perfick!
as to rtfm, yes I know about msdn; have a suitcase full of their Cd's and a
couple of doorstop sized books on SQL Server, but I am not [paid as] a DBA,
and I don't have the time to learn how to do it in v2000, v2003, v2005, or
the soon to be misnamed 2010 'new decade edition' -
I just wanted a quick fix (again, thanks Derek!)
thanks from an unusually (?) grumpy - AndyD 8-)#
**********************************************************************
Manchester City Council supports Smokefree England - 1 July 2007
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
Please contact [EMAIL PROTECTED] with any queries.
**********************************************************************
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
