Auto-generated statistics names can seem like they are entirely random, but there is a method to the madness. With a little effort and a bit of TSQL trickery, we can decode those names and reveal what the names really mean.
Three very powerful but simple hacks that can give you back dozens of minutes per day.
One of the best coping mechanisms for Impostor Syndrome is the use of learned behaviors. This article shares some of these coping mechanisms and learned behaviors.
When running into error 1326, it makes plenty of sense to try to create a backup dump device (only as a testing exercise) as well as test the connectivity to the UNC path from the local server instead of a remote server.
Every once in a while there is an extremely valuable tool that comes along. While the footprint and use frequency of this tool may not be that big, the tool is essential to making the DBA job easier to do. I recommend getting this tool – especially if you have ever run into SSPI issues.
At best these phantom backups cause undue headache in troubleshooting. At worst, they make it impossible to recover in the event of a database related disaster. Join me for a troubleshooting journey involving phantom backups.
Yes Virginia, there are ghosts in your database. More specifically, there are ghosts in your SQL Server database. They are not there to haunt you. They are not there just for this holiday season (speaking of Halloween Month).
How can there be ghosts in the database?
Why would there be ghosts in the database?
Do they happen because somebody issued a KILL statement?
Working with PowerShell brings a lot of advantages and power to help manage a server. The more current your PoSh version, the more efficiently you will be able to manage your server. Sometimes getting to the current PoSh versions comes with a little pain such as ISE crashes.
SQL Server comes with a default SQL agent job installed (for most installations) to help manage the collection of system health data. I would dare say this job is ignored by most people and few probably even know it exists. This job is the syspolicy_purge_history job.
Working diligently as any good DBA might, you have established maintenance routines for each of the SQL Servers under your purview. Then a small problem occurs: Index Cannot Be Reorganized…