If you haven’t heard of DLM Dashboard, let me fill you in – it’s a new free tool for helping SQL Server DBAs and developers know what database schema is deployed where. One of the main ways DLM Dashboard does this is by sending an email notification as soon as it spots any unexpected schema changes.
DLM Dashboard’s email notifications have proved hugely popular. Over the last 6 months we’ve had heaps of feedback from users telling us how they’ve avoided problems by being notified of unexpected schema changes.
But what if you don’t live in your email inbox? Something that most users don’t know is that receiving notifications in your inbox is just the start of what you can do with DLM Dashboard. In fact, the possibilities are practically limitless. You can use DLM Dashboard’s email notifications to automate a vast array of tasks, like alerting you and your team via HipChat, or automatically creating a new issue on GitHub when an unplanned schema change is made.
All you need to do is configure DLM Dashboard’s email notifications to be sent to a web integration service such as Zapier or IFFFT. Once connected, you can configure the email notifications to trigger automated tasks with a huge number of services and apps.
How does this work?
When a schema change is made to a database that DLM Dashboard is watching, an alert is triggered. DLM Dashboard then sends an email notification to your chosen web integration service. The web integration service receives the notification email and, depending on the contents of the email, triggers an automated task within your chosen app or service.
Don’t worry if you’ve already set up email notifications to be sent to your email address; DLM Dashboard allows you to send notifications to multiple email addresses. Most web integration services allow you to configure email addresses which in turn trigger an action.
So what exactly can I do?
Pretty much anything! The only requirements are that you’ve set up DLM Dashboard email notifications and have an account with a web integration service (e.g. Zapier or IFTTT). Here are a few of the ideas we’ve come up with to help you and your team manage schema changes:
- Receive a team Slack or HipChat alert when your database schemas change
- Create a Trello testing task every time you push a change to your testing environment
- Create a Jira or GitHub issue or a Zendesk ticket every time your production database drifts from the expected schema
- Keep a detailed record of all database changes in Google Sheets
- Track the frequency of database changes with Geckoboard
- Turn on a red alert light whenever your production database drifts with Philips Hue and IFTTT
How do I get started?
All you need to do is set up email notifications in DLM Dashboard and configure them to be sent to Zapier or IFTTT. You can then create an automated task which is triggered whenever an email is sent. I’d definitely recommend spending some time experimenting with all of the various integrations and services – as I said before, the possibilities are limitless!
If you’d like more detailed instructions, why not read my follow-up article? It includes an in-depth explanation of how to send Slack IM alerts to you and your team whenever your database schemas change.
In the meantime – have fun experimenting!
Was this article helpful?
Also in Blog
In the first post in this series, I talked about the challenges for the US Government sector when attempting to introduce DevOps. The sector lags behind others such as Financial Services on every meas...
Also in Software development
When deploying new versions of a centralized application like a web service, there’s a strategy you can use to direct production traffic to the new version only after it has been successfully de...
Also about DLM Dashboard
As a DevOps engineer at Redgate, I’m one of those responsible for keeping the systems going behind the scenes. That’s everything from the internal systems and databases to the infrastructure that ...