SQL Server 2008 BLOB data

Trace Flags

Determine SQL Server memory use by database and object

For many people, the way that SQL Server uses memory can be a bit of an enigma. A large percentage of the memory your SQL Server instance utilizes is consumed by buffer pool (essentially, data). Without a lot of digging, it can be hard to tell which of your databases consume the most buffer pool memory, and even more so, which objects within those databases. This information can be quite useful, for example, if you are considering an application change to split your database across multiple servers, or trying to identify databases that are candidates for consolidation.

Bad Passwords

Lock Escalation

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