![]() ![]() This was going to be a tedious process, so lets automate it. So the first thing to do is to is to work out a time window when the data went missing. And at the moment we don’t even know if that’s a needle, a pin or an apple seed Searching 3 days worth of it would be like looking for something in a hay stack. The transaction log holds a LOT of information. SQL Server won’t do any data modification without it being written into the log, as SQL Server doesn’t count the transaction committed until it’s logged as it needs it for recovery after a restart. The name of that audit is the Transaction Log. It’s just awkward and complex to read and search. Now, as any DBA knows, SQL Server comes equipped with a bit in ‘audit’ for any operation that modifies data. We’re now on the 6th Febuary, so that’s a window of just over 3 days it could have gone missing. A slight break through is that someone clearly recalls seeing the data at 09:45 on the 3rd of Febuary, but that’s as good as it gets. Now if there’s nothing in the audit trails, and noone is confessing then that doesn’t leave me with very much to go on. Data has gone ‘missing’ from a corporate system, and there’s nothing in the audit trail about when it went missing or how it went missing. ![]() Nice quiet day in the office, busily cracking through the To Do list when suddenly something pops into the ticketing system as a P1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |