Brandie Tarvin (3/3/2015)
Ed Wagner (3/3/2015)
Brandie Tarvin (3/3/2015)
Ed Wagner (3/3/2015)
Brandie Tarvin (3/3/2015)
Ed Wagner (3/3/2015)
Brandie Tarvin (3/3/2015)
Not to be weird, but...YAY! I HAVE MY FIRST SUSPECT DATABASE!
It's a non-prod reporting database that doesn't get backed up, so now I can really some practice in. @=)
Of course, I could cheat and just restore it from the OLTP database that it usually gets restored from, but that's too easy of a solution.
(rubs hands together gleefully). Is it twisted that I'm about to enjoy myself this morning?
I don't think it's completely twisted that you enjoy it, but it's pretty nice that you have an ace up your sleeve to rebuild it if nothing else works. So, I guess congratulations are in order on your suspect database and a chance to play. 😉
And now I am heart broken. It's only a space issue. Some nimrod (probably me) restored the DB to the wrong drive.
Bleargh. And here I thought I was going to be able to do SCHTUFF. Still, I might as well follow the insufficient drive space issue along to see what else I can find before I fix it.
Sorry for your loss. I know what you mean about wanting to try stuff out.
Doesn't Paul Randall have some suspect databases and ones that have integrity check errors available for download? It's been a while, but I think I remember downloading some a while back for testing. You might be able to play after all.
Well, I put it in emergency mode and am running DBCC CheckDB (no params) against it to see what comes up. We'll see what I get to learn (although, I already know to avoid the repair with data loss option).
Paul has corrupt databases available at http://www.sqlskills.com/blogs/paul/corruption-demo-databases-and-scripts/.
Enjoy and have fun with it.
Thanks for the link!
My db, predictably, has "CHECKDB found 0 allocation errors and 0 consistency errors in database". Heartbroken, I tell you. I'm just heartbroken.
And now I'm trying to take it offline. And apparently failing miserably.
Brandie, if you want, I can send you a script to create and then corrupt a database. I use this in the hand's on portion of an interview where I judge someone's ability to handle this situation.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes