Those who are subscribed to my newsletter will receive the exact time of the next corruption challenge. For those who have not subscribed, just keep checking back to find out when the next Database Corruption Challenge begins. Here is the latest update on how the challenge has gone so far: Week 1 was just a wild idea that I had to …
Database Corruption Challenge #5 is coming soon. Those who subscribe to my newsletter will know the exact date and time of the next Database Corruption Challenge. Lets take a look back at the winners from the previous challenges. Week 1 – Brent Ozar Week 2 – Rob Farley Week 3 – Randolph West Week 4 – Randolph West If you …
Congratulations to Randolph West who won the corruption challenge this week with the following solution which restored all of the data. First he restored the database to get started. Note some of his code and comments have been reformatted to better fit in the blog format. Restore database. I use KEEP_CDC and KEEP_REPLICATION because of the hints you dropped in …
Corruption Challenge Week 4 – The Winning Solution Read more »
You have a need to keep track of all insert, update and delete actions on a table, or multiple tables. As you consider solutions, you might think about using a trigger, however triggers have their own baggage. You consider using the OUTPUT clause to log to a changes table, but then realize that the output clause cant be enforced. Then the …