So how do you drop databases?

Do you use a simple DROP DATABASE statement?

Do you detach the database and remove the files manually?

Do you use the GUI?

Run these two quick and dirty queries for me:

SELECT COUNT(*)
FROM   msdb.dbo.backupset

SELECT COUNT(*)
FROM   msdb.dbo.backupset
WHERE  database_name NOT IN (SELECT name FROM master.dbo.sysdatabases)

So how much of your MSDB database is filled with backup history of databases that have long since been dropped from your instance?

MSDB love and care is not something that usually gets alot of press but if you’re a stickler for wanting to keep things neat and tidy take a look at the information in your MSDB and whether or not you’re storing (and backing up) more data then you need to.

Want to rid yourself of some MSDB bloating?

SELECT DISTINCT(database_name)
FROM   msdb.dbo.backupset
WHERE  database_name NOT IN (SELECT name FROM master.dbo.sysdatabases)

So now that you have a list of those old databases that still have backup history kicking around… now what?

Don’t jump the gun and write a DELETE statement for msdb.dbo.backupset… what about the other backup tables like backupfile, etc?

Answer: msdb.dbo.sp_delete_database_backuphistory

EXEC msdb.dbo.sp_delete_database_backuphistory @db_nm = N'<<DATABASE_NAME>>'

Using this system stored procedure you’ll ensure that you’ve removed all the backup history for the specified database.

(As always, please use with caution)

Enjoy!!

If you move MSDB your notifications will stop working.  Why you may ask?

It’s because the ENABLE_BROKER configuration is set to false when you move MSDB.  Now I can’t seem to find (google) any information as to WHY this is (please send comments if you have further info) but in order to get your notifications up and running again you’ll need to run the following command:

ALTER DATABASE msdb SET ENABLE_BROKER;

If this takes a while to run then chances are you are being blocked by another process (chances are the SQL Server Agent)

If you’re interested in reading more here is the Microsoft BOL Link on moving system databases.

Enjoy!!

http://benchmarkitconsulting.com/colin-stasiuk/2009/01/21/sqlagentreaderrole-not-so-reader/

Below is the solution I’m working with to give developers access to the Job Activity Monitor but NOT the ability to create new jobs.

I know adding a role to a system database is not ideal but I’m open to other suggestions


USE [msdb]
GO
CREATE ROLE [SQLAgentReadOnlyRole] AUTHORIZATION [dbo]
GO
EXEC sp_addrolemember N'SQLAgentReaderRole', N'SQLAgentReadOnlyRole'
GO
DENY EXECUTE ON OBJECT::msdb.dbo.sp_add_job TO SQLAgentReadOnlyRole
DENY EXECUTE ON OBJECT::msdb.dbo.sp_add_jobserver TO SQLAgentReadOnlyRole
DENY EXECUTE ON OBJECT::msdb.dbo.sp_add_jobstep TO SQLAgentReadOnlyRole
DENY EXECUTE ON OBJECT::msdb.dbo.sp_update_job TO SQLAgentReadOnlyRole
DENY EXECUTE ON OBJECT::msdb.dbo.sp_add_jobschedule TO SQLAgentReadOnlyRole

So after you create your new SQLAgentReadRoleRole you can add role members to it and they will be able to view the Job Activity Monitor but will not be able to create new jobs… use at your own risk as like I said… I’m still working with it but this is the direction I’m heading right now.

If anyone has a more elegant solution I’d be very interested in seeing it.

Why you grant them SQLAgentReaderRole access in msdb…. WRONG

http://technet.microsoft.com/en-us/library/ms188283.aspx

The SQLAgentReaderRole is a reader role for the jobs that currently exist but wait here is where the good (or bad depending on if you’re in a good mood or not) part comes in.

Me – “Hey Mr Developer I made this change in UAT you should now be able to view the job activity monitor… just for my own curiousity I’m going to come by can you try to execute, delete, update jobs that are there.  ”

Mr Developer – “nope… can’t do anything like that”

Me – “Great… can you create a new job”

Mr Developer – “Yup”

Me – ” *sigh* I hate (and by hate I mean it in a love/hate kinda way) Microsoft

That’s right folks… SQLAgentReaderRole can create jobs.  So although it’s called SQLAgentReaderRole be careful granting this access cause whomever you add to this role can create new jobs.

UPDATE will come if/when I find or create a usable solution