Database Recovery

How to Find the Reason Why TempDB is Full in Your SQL Server

If the temp DB database of your SQL Server runs out of space, it can cause major disruptions in your production environment and can interrupt user applications from successful completion. If you are using a script to track temp DB size, append the script from this article to identify the root cause for the temp DB filling. Tempdb full – a common scenario Poorly written queries might create several temporary objects resulting in a growing tempdb database. This will end in disk space alerts...

Read more »

How to Batch Set the Error Log Location for Multiple SQL Server Agents

If you are given a task of changing the SQL Server agent's Error log location for a single SQL Server instance, you could easily do that by using SQL Server management studio. However, if the same task must be completed for almost 1000 SQL instances, you might take a month to complete it. In this article, we will learn how to update SQL Server agent's Error log path through TSQL. For a single instance To set a new location for the SQL Server agent’s error log, using SQL server management...

Read more »

How to Track and Monitor All Database Owners in Your SQL Server

Having a check on database owners is very important. You might hit a service broker problem and then realize that the root cause was a windows login of an ex-employee and it was set as the database owner. If you proactively track database owners, you will never meet such issues in your work environment. Not DBO In this article, we are dealing with database owner and not do or db_owner. DBO is a user, it’s a database concept and db_owner is a fixed database role. Log it From your central...

Read more »