Discover the true impact of bad SQL Server database deployments

See exactly when a database deployment is made and how it affects the performance of your SQL Servers

Download Redgate's SQL Toolbelt

Deploying database changes to production is an everyday part of working with SQL Server. But when something goes wrong, a bad deployment can cause a whole world of pain – slow performance, loss of productivity, and even loss of revenue.

Tracking the root cause of the poor performance can be done, but it takes time to pinpoint that the cause was a bad deployment.

To speed this process up, and give you a better indication of what's happening on your servers, SQL Monitor now shows when a deployment has taken place, and puts it in context with SQL Server performance metrics.

You quickly see the true impact a deployment has on your servers and can instantly tell if the deployment is the smoking gun you've been searching for.

See it in action in this 2-minute video

Try SQL Toolbelt free for 14 days

How does it work?

1. Deploy

Deploy your database change using one of Redgate’s deployment tools: SQL Change Automation, or SQL Compare.

2. Monitor

These changes are picked up by SQL Monitor and displayed in the server overview screen

SQL Monitor picks up your changes and displays them in the server overview screen

You don't need to set up or configure anything – SQL Monitor will catch changes made by anyone in your company.


To take advantage of this capability, you need to run SQL Monitor 7.1.5+, plus SQL Compare 13.0.3+, SQL Change Automation 2.0.18+, or ReadyRoll 1.14.13+.

Your deployment tool must be licensed as part of the SQL Toolbelt, rather than as a standalone product.

The user who's deploying will need execute permission on xp_logevent, the dbowner role on the master database, or be a System Administrator.

To get started, download the latest version of The SQL Toolbelt

Download Redgate's SQL Toolbelt