Analyze and Correct a large SQL Server MSDB Database

It has come to my attention that some of our MSDB databases are getting what I would consider large for a system database. Some of our MSDB databases are over 2 GB which is a little perplexing because I know we do not create any user defined objects in that database. Can you give me some insight into the issue? I know we have this issue with both SQL Server 2000 and 2005 instances.

DBA Morning Check List

This article helps the DBA find and fix issues quickly by creating a DBA Morning Checklist.

Backups

When sp_depends fails

sp_depends may not always return accurate information

Delete files older than n-days via T-SQL

Delete files on a fileshare leaving behind files not older than n-days.

Moving System Databases

Verify Last successful CHECKDB on all databases

Creates a resultset that expresses the last time a successful CHECKDB was performed on every database in the instance.

Does not work on SQL 2000.

SQL Server Scalabilty - An Introduction

A brief introduction into the world of scalability, presenting at a high-level the various options

SQL Server DBA Fights a Demon

An interesting tale of David Bird's fight with tempdb.

Compare Different tables from 2 Databases

List tables that have different tables and column