T-SQL Tuesday is a monthly blog party for the SQL Server community. It is the brainchild of Adam Machanic (b|t) and this month’s edition is hosted by Kennie N Ponotoppidan (b|t), and covers the topic “The Daily Database WTW” (yes, I know, I changed it to “What the What”. Personal preference…)
Kennie is asking us to post about the most insane thing we’ve seen in SQL Server. Mine was so bad I’ve already blogged about it here, so I’m just going to copy and paste…because I’m lazy 🙂
I walked into a new client in 2015 and found this, all one one server:
o SQL 2008 R2, RTM
o Incorrect Memory configuration
o Full recovery model on data that only changes once a week at most
o ZERO documentation of server settings
o New data is imported to a new table and a UNION ALL query is modified to add that table
o ZERO documentation of code/databases
o Stored Procedures have no comments, poor formatting and developer names in the name of the proc
o Autogrow is 1MB, data imports are hundreds of MB each
o Everyone is sysadmin, probably including you…
o Change control process is intentionally shortcut and ignored on this internal production system
o Ownership changed to me in December, then was yanked back 3 weeks later with developers overwriting my fixes in prod.
I still feel the stench of that assignment…but its slowly wearing off 🙂
Thanks for reading!