Last Updated on May 9, 2011 by John Morehouse
Yes, I know that it’s Friday. I know that I’m about 5 days too late for this, but I figured, hey, it’s my blog, I’ll post when I find the time right? So, it’s Friday evening, the breeze is blowing, the wife is out with the girls (thus blogging time for me!), the boy is asleep and the dishes are done. Perfect time for . . .
MeMeFriMonday! Yeah, that’s right. I’m going to post my MeMe Monday post on Friday. Aren’t I such a rebel? Watch out, I might turn into a zombie rebel!
Without further ado, 9 things that could go wrong with SQL Server that isn’t the disk:
- Cursors
- GUID’s
- Horrible Database Design
- Lack of foreign keys
- Lack of primary keys
- Database Developer Wanna Be’s
- Third Party Applications
- Spatial Indexes
- SA rights for everybody! (Poor Security)
Of course, these are not in any particular order and there are probably ton of other things that will come to mind later, but these are the ones that showed up in my mind when I sat down to write this.
Enjoy!
© 2011, John Morehouse. All rights reserved.
I’d rather read it late, than not at all. Thanks for the list!
I like item 7, and it got me to thinking… In a corporate IT shop, the corporation is the 1st party. If it’s a virtualized environment, VMWare or Zen might be the 2nd party. That would make Microsoft the 3rd party.
I’m just sayin’
That’s awesome! Didn’t even think about it in that fashion, but I like the way that you think! 😉