• Lowell (11/23/2010)


    a whole lot of knee jerk reactions about "but it's not supported!", but since it works on SQL 2008 ( and someone reported it works all the way thru Denali), and your server is going to be around a while, I don't see any advantage in poo-pooing the effort put in the script.

    how about this typical example that gets about 10 posts a week on "how can i get my data back":

    premise:

    database is in FULL recovery, but noone has setup a backup strategy. No backups available anywhere.

    someone updates the INVOICE table without a WHERE statement...say setting the INVOICEAMT to $100... or someone DELETES the table without a WHERE statement.

    the upcoming articles on how to examine UPDATEs and DELETEs ( where this article covered INSERTS) would be the difference between being able to handle the situation and having to look for another position somewhere, as the company closes down due to data corruption, right?

    now, if you can point out the recommended way to handle that specific situation without using undocumented features, and without changing the parameters of the issue (don't say "well there shoulda been backups) I'm listening.

    Any DBA caught in this specific situation should put his head between his legs and pucker his lips to kiss his rear end goodbye. This is one of those avoidable situations they created unemployment insurance for.