5 September 2017
5 September 2017

Unearthing Bad Deployments with SQL Monitor and Redgate’s Database DevOps Tools

Sudden performance issues in SQL Server can have many causes, ranging all the way from malfunctioning hardware, through to simple misconfiguration, or perhaps just end users doing things they shouldn’t. But one particularly common culprit is when deployments go wrong: I don’t know a single DBA who hasn’t been burned by a bad release.

To help, hundreds of thousands of developers and DBAs use Redgate’s Database DevOps solution to automate the build, test and deployment of their database changes. By implementing reliable, scalable and repeatable processes the risk of introducing defects into production is significantly reduced. But what if the change behaves differently to expected in the production environment?

An example

Here’s the top of SQL Monitor’s Server Overview screen – the sort of screen you might be looking at after learning that a server’s running slowly. SQL Monitor raised a High CPU alert at 8:31, and it’s pretty clear that something went dramatically wrong shortly beforehand, but what?

At this point, the challenge is to narrow down the root cause as quickly as possible. As the DBA, this kind of investigation turns you into a detective, where every minute taken to find the problem has a real cost to the organisation’s productivity, as well as to your reputation.

While bad deployments can eventually be tracked down by following other avenues, SQL Monitor now makes the cause of the problem instantly obvious by surfacing deployment information generated by Redgate’s deployment tools (SQL Change Automation and SQL Compare) in context within SQL Monitor.

You now see the release marked on the timeline immediately below the performance data, and upon hovering, we see which database was deployed to, as well as by what tool. This saves valuable time by instantly revealing the smoking gun, with no further exploration needed.

This capability is part of Redgate’s SQL Toolbelt and is available for any changes made by the latest versions of SQL Change Automation, or SQL Compare. There’s zero setup needed, either in SQL Monitor or in the deployment tools, so changes made by anyone in the organisation using these tools will automatically be shown.

We’ll be improving this feature further, with information about the user responsible for making the change, and potentially the build number in the case of automated deployments, making it even easier to correlate changes in key metrics with specific release activities.

What now?

Check out the latest version of SQL Monitor, or read more about Redgate’s Database DevOps solution. As usual, we’d love to hear your feedback. How can we improve this further? Just drop an email to sqlmonitorfeedback@red-gate.com.

Thanks!

Ben

Requirements

To take advantage of this capability, you’ll need to be running SQL Monitor 7.1.5+ along with SQL Compare 13.0.3+ or SQL Change Automation. This capability is also compatible with DLM Automation 2.0.18-[final version] and ReadyRoll 1.14.13-[final version]. Additionally the deployment tool must be licensed as part of the SQL Toolbelt, rather than as a standalone product. The user making deployments will need to have execute permission on xp_logevent (or can alternatively either have the dbowner role on the master database, or be a sysadmin).

Share this post.

Share on FacebookShare on Google+Share on LinkedInTweet about this on Twitter

You may also like

  • Webinar

    How DevOps can help you stay ahead of the competition

    In this webinar, Microsoft MVP Steve Jones welcomes DevOps expert Bob Walker, Solution Architect at Octopus Deploy, to discuss how taking a DevOps approach paves the way for staying ahead in business.

  • Article

    How to Detect SQL Injection Attacks using Extended Events and SQL Monitor

    Even if all precautions have been taken to prevent SQL Injection attacks, as laid out in the OWASP website, it is still wise to be able to detect if an attempted attack is taking place, and it is essential to know if such an attack is successful. There are several strategies for detecting SQL Injection

  • Article

    Scaling SQL Monitor to Large SQL Server Estates

    Most organizations are finding that the size and number of databases that need to be monitored is increasing, unlike the number of people available to do the work. Now that it is possible for the organization to scale out to cloud-hosted databases, the constraints of the available infrastructure have ceased to govern the growth of

  • Webinar

    Extending DevOps to the database: branching and merging

    Join our webinar to learn how Redgate’s Database DevOps solution works to improve your database development and deployment processes. With a focus on branching and merging, we’ll show how Redgate tools plug into Visual Studio Team Services (VSTS) to enable the build, test and deployment of your database changes.

  • University

    Take the SQL Monitor course

    This course takes you from installation and configuration, all the way up to getting the most out of the advanced features in SQL Monitor to help you proactively monitor your SQL Server estate. Learn how to explore in-depth issues in your environment, run an analysis, manage alerts, create custom metrics, and more.

  • Forums

    SQL Monitor Forum

    Real-time SQL Server performance monitoring, with alerts and diagnostics