Sometimes you see someone with toilet paper sticking to their shoe, their shirt tucked into their underwear, or badly in need of a tissue to get rid of whatever that is hanging out of their nose. It’s only right to find a discreet way to let them know they should do some quick cleanup before they get completely embarrassed.
The same embarrassing “oops” exist for SQL Server. There are some practices and configurations which just make it look like the DBA may not have learned about this “internet” thing yet.
But, truthfully, it’s very simple to accidentally embarrass yourself. Here are the top 10 (well, 11) signs that your skills or your SQL Server are badly in need of an update:
- You have databases that haven’t been backed up recently
- Your last DBCC CheckDB is over 2 weeks old
- You have jobs that shrink files– or autoshrink enabled
- You truncate your transaction log
- You’re running the RTM version of SQL Server
- You use SQL 2000 style commands like DBCC SHOWCONTIG and DBCC REINDEX on later versions of SQL Server
- Priority Boost is enabled
- Power savings is enabled
- App accounts have SA or db_owner permissions
- It’s a 32-bit SQL Server
- Your tempdb has only one data file
Even if you know better, have you checked your servers to make sure that you don’t have toilet paper on your shoe without realizing it? Run our free sp_blitz® script to check for most of these issues, and more.