Memory

A story of corrupted Master database in SQL Server 2008

This is a real-time production issue I faced with one of our clients

Find SQL Server data and log files that are almost out of space

On many SQL Servers database file size, either data or log, may be restricted to a maximum size to ensure there is adequate space on the server. The problem with this is that if your data or log file runs out of space you will get an error message

Find SQL Server databases where log file is too large

I support thousands of databases and I'm running across situations where I have a database that has a data file of a couple hundred megabytes and the associated log file is gigabytes in size! I understand this is because I may not have my transaction log backups scheduled properly. What I'm interested in is an easy way to identify these situations where the SQL log file is too large, so I can go in and further analyze these problem databases without needing to look at each database.

Backup all databases & check backups

Stored procedure to backup all DB (chose user or system). You can do full, differential and log backups

Restoring Editions

TempDB Deleted Accidentally

TempDB is the ALU of the SQL Server and if somehow this gets deleted Server cannot start. Here is a solution of how to get the server started when TempDB is deleted.

SQL 2008 SP/CU Patching Through Windows Scheduled Tasks

Automate patch installations using the task scheduler and command line hotfix options for SQL.

Killing Statistics

Clean unused space when a variable-length column is dropped from a SQL Server table or indexed view

Whenever rows or columns are deleted from a table, SQL Server reuses space to accommodate new data. However, this is not the case when a variable length column is deleted. The space used by this type of column is not reclaimed automatically. Variable length columns can be of data types varchar, nvarchar, varchar(max), nvarchar(max), varbinary, varbinary(max), text, ntext, image, sql_variant, and xml. In this tip, I have tried to put forth a solution to reclaim this space and this should work for SQL 2005 and later versions.