After two great weeks of the database corruption challenge, week 3 is approaching. I have a few things to announce as we go into week 3. The database corruption challenge will run over 10 weeks at which point another challenge will begin, and everyone will start out with a fresh score, sort of like bowling. This post I am going …
Database Corruption Challenge Week 3 Approaching Read more »
When you are looking for deadlocks there are, like most things in SQL Server, more than one way to find the deadlocks. This article is specifically focused on using the SQL Server ERRORLOG file located in the LOG directory for the SQL instance. If you used the defaults on SQL Server 2012, this log would be at this location: C:\Program …
With week two of the Database Corruption Challenge being just as interesting as week one, and after seeing yesterdays blog posting showing the solution by Rob Farley, you might be thinking you are ready to take on corruption. If you are interested in giving the corruption challenge a try, please sign up for my newsletter so that you will be notified …
Database Corruption Challenge #2 – Alternate Solution Read more »
It is my pleasure to announce this weeks winners in the Database Corruption Challenge – Week 2. There were many great solutions submitted, and I hope that everyone learned something from this weeks challenge. My favorite part of the whole challenge was this post on Twitter… The whole goal of the Database Corruption Challenge is to help everyone …
Welcome to week 2 of the database corruption challenge. Hi, I am Steve Stedman and I have created this challenge to help the best and brightest SQL Server DBAs on the planet test their skills and to show expertise to the world. The winner last week was Brent Ozar, I would just like to congratulate him again on winning the …
The next Corruption Challenge will be announced soon. The Corruption Challenge from last week was a hit, and I am going to repeat it again this weekend. If you want to find out about the next corruption challenge, stick around, or register for my newsletter to be informed of when the challenge will begin. Related Links: Newsletter sign up Database …
Next Corruption Challenge – To Be Announced Soon Read more »
Most DBAs know the usual difference between TRUNCATE and DELETE FROM, however one not so obvious difference between the two is how things are handled if the table is corrupt. For instance, if you look at the corrupt database from the Database Corruption Challenge Week 1, you see the following If you want to clear out the corrupt Revenue table, …
Difference Between TRUNCATE TABLE and DELETE FROM Table Read more »
After posting the winning solution for Corruption Challenge 1 from Brent Ozar, I realized that he and I both solved the corruption by using the REPAIR_ALLOW_DATA_LOSS option on CheckDb. A very nasty move, however it did repair the corruption. After reading some feedback, one of the winners stated: As soon as he ran REPAIR_ALLOW_DATA_LOSS, I knew we weren’t on …
Corruption Challenge 1 – An alternative solution Read more »
As the weekend approaches and we head for another Database Corruption Challenge (DBCC) I want to remind everyone who is interested of being notified of the next event to sign up for my newsletter. Just click here to find out more about the newsletter. Sometime Friday I will announce the latest Corruption Challenge, those on the mailing list will be the …
Since the corruption challenge completed yesterday, I have had several request asking how I created the corrupt database. So here is the script that I used to create the Database Corruption Challenge 1. First the initial setup. Most of this I stole from a query training session that I did several weeks ago. All I really needed was a table …
Corruption Challenge 1 – how I corrupted the database Read more »