Kevin3NF

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.

Oops.

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.

Kevin3NF

Wow…its been a long time since something went so sideways I felt compelled to write about it….

But don’t mistake that for there not being any craziness!

ATTENTION ALL DEVELOPERS!!!!

If you are going to do a major upgrade to your very large database, please consider the following:

• YOU are responsible for your rollback plan. Nobody else.
• When you wake us up to rollback because your upgrade blew up, please give us a chance to get up to speed, before you start calling Directors and VPs.
• TAKE A BACKUP IMMEDIATELY BEFORE THE UPGRADE!!!!!
• Store that backup in a folder that does not have a cleanup/delete process attached to it
• Test this upgrade in your test/dev environment first.
• Don’t expect me to throw a teammate under the bus on a conference call.
• Don’t expect me to be on a conf call every 30 minutes…I’m busy cleaning this up.

Not only do you not get fries, you now owe me some! (Waffle fries from Chick-Fil-A will be just fine, thanks.)

That is all.

OK…if all 3 instances on a 3-node cluster suddenly start “timing out”, yet you can log directly in and query the databases…don’t you think you should at least look at the network components first?

Especially when the errors are showing on the client and web boxen…

Grrrrr….