Startup Stored Procedure Found

Blitz Result: Startup Stored Procedure Found

SQL Server can run stored procedures in the master database automatically whenever it starts. If you don’t know what these stored procs are doing, you could be in for some ugly surprises. For example, some third-party security auditing software automatically starts up extra traces whenever SQL Server is started, and those trace output files are written to the system drive. If you don’t know about those, the C drive can fill up and your server can stop dead.

This part of our SQL Server sp_Blitz script checks INFORMATION_SCHEMA.ROUTINES looking for stored procedures that are executed automatically on startup.

To Fix the Problem

Script out these stored procedures and review what they’re doing. If you’re not satisfied with what they’re doing, you can back up the stored procedure and drop it or simply disable startup stored procedures.

Return to sp_Blitz or Ask Us Questions

1 Comment.

Rudy Panigas
July 3, 2012 3:13 pm

Hello Everyone!

First I wanted to say thanks for the sp_Blitz stored proc!! It’s amazing what it finds!!

It reported something strange and maybe someone can shed some light for me (or turn on my light bulb).

I have a stored proc that started up automatically (Stored procedure [master].[dbo].[sp_MSrepl_startup] runs automatically when SQL Server starts up) and I lost at to how stop this without deleting the sp. I don’t have any replication turned on, so I don’t use this proc, but don’t want to delete it either.

Any suggestions?

Thanks for a great tool and site!!!

Rudy 🙂