I was participating in an email interview about my SQL career and opinions and one of the questions was basically “What’s the worst SQL thing you’ve inherited?”
I gave them this list:
Really….all that on one server!
Upgrade your fries broseph!!!
Plain ‘ol English….
You walk into Starbucks and there’s 1 guy ordering. He finishes, then you order. That’s blocking, and its perfectly normal, expected and acceptable.
You walk into Starbucks and there’s 1 guy ordering for 15 people in his office. You’re willing to wait, but not forever. That’s moderate blocking.
You walk into Starbucks and there’s 1 guy ordering, 7 people in line and they are all ordering drinks with names too long to remember….you walk out. That’s excessive blocking with a failed transaction (you).
Blocking in SQL Server is just transactions that need the same resource lining up to take their turn. Its by design and is a good thing. Excessive blocking needs to be fixed.
You have 2 children. Each has a toy, and at the same time they each grab for the toy the other one has, but won’t let go of the first one. This is a Deadlock. SQL Server has a built-in process to resolve this. They gave it an official name, but I call it “Mom.” Mom steps in and breaks it up…automatically. This is a code issue much of the time…profile it, trace flag it, whatever..but find and fix your application code. If its not your app code, it could be just performance related…tune or rebuild some indexes may get you there. Start HERE for troubleshooting deadlocks.
Does that help?
They are NOT the same thing…Deadlock is bad, Blocking is part of the engine…to a point.
Next up (maybe): Replication and Log Shipping are not the same thing…quit using them interchangeably, especially when you mean “Clustered”
Have a nice day!
Short one today:
I tell the upper level manager that ALL of his data is at risk due to one root issue. Got him good and scared…he totally believed me. And did absolutely nothing to fix it, or even explore possible fixes, which would have been a good exercise.
Swept it under the rug.
Seriously…one disgruntled employee with minor hacking skills and this place goes away.
No fries for you.
** This was a long time ago, so no…you can’t guess who I’m talking about by reading my LinkedIN profile 😀
With apologies to Nat King Cole 🙂
Database backup failing
Write on “D:backupMyDatabaseMyDatabase_20150208104103883_D.bak” failed: 665(The requested operation could not be completed due to a file system limitation) [SQLSTATE 42000] (Error 3202)
Hey, customer…let not put backups on O/S compressed drives please.
Oh…and why do you have your MDF/LDFs on the same drive…also compressed?
Resolution – punt it back to them and tell them SQL Server on compressed drives is unsupported config by Microsoft and by me. Uncompress and expand or add a drive and uncompress.
Sheesh. How many worst practices can you get in one server?
Short and sweet…
Ticket for error 1105. Teammate response: No blockings on server, monitor 4 days.
Ticket for error 601. Teammate response: No blockings on server, monitor 4 days.
Ticket for login failed. Teammate response: No blockings on server, monitor 4 days.
I. Kid. You. Not.
Someone needs to be fired. Or congratulated for making me look like a SQL SERVER GENIUS!!!! by comparison.
That is all.