Configuring SQL Monitor

I got to meet with the team who creates SQL Monitor today. (Yes, I have a very cool job!) Since I’m kind of new to SQL Monitor, they wanted to know what I didn’t like about it. Well, I had a hard time coming up with anything because I found it so easy to use. Once I had watched a couple of videos, I was able to find my way around easily. The tool seems very complete as well. Everything that I could think of that I wanted to monitor was either there by default or a script to add it as a custom metric was available.

Finally, I thought of something. I wanted to create an exception list for the ‘Database Unavailable’ alerts. When I went to the to the configuration page, I was hoping to see a way to add a database name that was set offline on purpose. This is what I saw:


I didn’t see any way to set up an exception list. It would get annoying really fast to be alerted about an offline database that was purposely offline.

I knew that it could be set across the organization, group, and instance. I didn’t realize, however, that it could also be set at the database level. Just by drilling down, I could turn this alert off for an individual database!



By default, settings are inherited from the organizational level. Below that, you can customize at the SQL Monitor group, server, instance and database level. For example, there are probably some metrics that are important for production servers that you don’t care about for development servers.

I’m back trying to think of something I don’t like about SQL Monitor. I’ll keep you posted about that. If you want to play with SQL Monitor, check out this live demo.  It’s actually monitoring Redgate’s live SQL Server instances. Enjoy!

Posted in Database Administration | Leave a comment

My First Look at SQL Monitor

I’ve used other tools for monitoring SQL Server, but this was my first look at SQL Monitor made by Redgate Software.

The first step was just to download the software and install it. It comes as part of the Redgate SQL Toolbelt, so I just had to make sure I selected the right tool from the bunch.


After installing, I had to point it to an existing SQL Server where a database would be created, and two services would be set up. Next, I just had to supply the instance that I wanted to monitor.


Since I was just setting all this up on a VM for a SQL in the City Streamed session, I installed everything on the same box. In a real production environment, you would probably set up a dedicated server for SQL Monitor. SQL Monitor is made to scale to hundreds of instances, so you don’t want it affecting any instances that you intend to monitor, and I also found that it needs to have enough memory to function properly.

One of the nice things about SQL Monitor, is that you do not need to install any client software. It’s completely web based. I tried it in Edge, IE, and Chrome and found no issues.

After launching the web page, I saw that it had already picked three problems with my instance! I saw those notifications less than five minutes after downloading the software. I was already impressed!


I spent some time watching videos on the Redgate site and YouTube to learn more about the tool. In this case, since I would be presenting, I wanted to feel confident and not stumble around. I found that once I understood the layout, finding my way around was easy.

If you count the Availability Group alerts, there are about 40 alerts built-in, and you can decide which merit an email notification.


Depending on the alert, you can configure them to meet your own requirements. For example, the “Log Backup Overdue Alert” can be configured for three thresholds. You may want to set different alert levels depending on how long since a transaction backup was performed.


Another very cool feature is the ability to add custom metrics. Many of these were contributed by members of the Friends of Redgate program. I started out with a list of things I want to see in this type of tool. Between the built-in alerts and the available custom-built alerts, I found everything I needed.


For those of you managing large SQL Server estates, be assured that this tool has a fantastic interface for viewing the status of hundreds of instances at once. Here is a look at our demo site which is running live against Redgate’s own production servers. You can play with this all you wish without breaking anything.


Once an alert has been raised, drilling into it gives you quite a bit of information. You’ll see the performance metrics during that time period and a description of the problem. The description will get you started solving the issue.


Overall, I was really impressed with SQL Monitor. It’s simple to install and use. You’ll spend some time making changes to the configuration, but it will start working immediately even if you don’t get to that right away.  

Posted in Database Administration, SQL Server Administration | 2 Comments

Live from Cambridge!

Every year, I present at eight or ten events plus user group meetings, either in person or remotely. Due to travel costs (yes, speakers pay their own way to events) and time, I’ve stayed in the US except for one event in Montreal almost ten years ago.  I love adding new states to my list of states where I have presented, but I decided that I should start adding new countries as well.

Again, that money and time thing has kept me close to home, but now my goal will be achieved next week! When I set goals, they are usually met, but not always in the ways I expect. Next week, I will be part of Redgate’s SQL in the City Streamed. This event will be broadcast live from Redgate’s headquarters in Cambridge, UK.

My session is “What SQL Server performance metrics should you monitor?” I’ll talk about my favorite things to watch out for as well as how to troubleshoot some common problems. I’ll be joined by MVPs Steve Jones and Grant Fritchey, so please tune in!



Posted in Uncategorized | Leave a comment