Take the 2019 State of SQL Server Monitoring Survey: Here’s What’s in It For You

Calling all Database Administrators, Developers, Analysts, Consultants, and Managers: Redgate has a survey open asking how you monitor your SQL Servers.

Take the survey before April 5, 2019.

Your time is valuable. The survey will take 5 – 10 minutes to complete. That’s not a ton of time, but it’s a noticeable part of your day, and there should be something in it for you. Here’s why it’s worthwhile to take the survey.

Database use patterns and monitoring trends are valuable to everyone in the community — and we’ve been missing out on this trend information!

This isn’t the only survey from Redgate — you may also have heard of the annual State of Database DevOps Report.

But this survey is different in important ways: it asks how you manage and monitor your SQL Server database environment, regardless of whether you think about DevOps at all.

Redgate shared the results of the State of SQL Server Monitoring Survey with readers last year, and will do so again in 2019. 2018 was the first time we know of that a survey of this kind had been done, and it will be especially interesting to notice what has changed in the past year.

If you fill out the 2019 State of SQL Server Monitoring survey, you’ll get an advance copy of the results by email

The results will help you understand:

What do other DBAs, Developers, and IT Professionals see as their biggest challenges over the coming year?

In last year’s report the biggest challenges were seen as:

1. Migrating to the cloud

2. How to deploy changes faster to larger environments

3. Protecting data – especially for compliance reasons

2018 State of SQL Server Monitoring Report

I’m curious to see if these priorities have changed after a year. With GDPR implementation having come to pass and more states and countries around the world passing increasing privacy regulations, I suspect that ‘protecting data’ may move up from number 3 on the list, but I won’t know until we see the data.

How much time do your peers spend examining SQL Server health and resolving issues?

This is a great question on the survey — and I think this one is absolutely worth some reflection after you take the survey (and after the results come out). Do you spend more time firefighting than you should? If so, what ideas you have to change that?

At what point to most organizations move from manual monitoring to a third party tool?

If you work for a growing company and are interested in making the case to purchase monitoring to your management, it may be useful to know information like this…

Respondents with fewer than 10 servers were twice as likely to rely on manual monitoring as to use a paid-for tool. Those with 10 or more servers were more likely to use third-party software.

2018 State of SQL Server Monitoring Report

Survey results will help you prioritize what to learn

Are you curious as to whether you should learn another database platform, such as MongoDB, Oracle, MySQL, Cosmos DB, or PostGres? The survey will show how much respondents report that they are using each platform, and whether they think the amount will increase or decrease.

Want to know whether you should invest time (and maybe ask for some budget) to explore cloud technologies like Azure Managed Instances, Azure SQL Database, or Amazon RDS? The survey will show how many of your peers are using each one.

Also, You Could Win Money

Everyone who completes the survey and provides their details at the end will be entered into a prize draw to win a $250 Amazon Voucher (or equivalent in your local currency).

Previous Post
Why to Avoid Using the Current Database Name in Object Definitions in SQL Server
Next Post
Upcoming full day training: “How to Architect Successful Database Changes”

Related Posts

No results found

3 Comments. Leave new

  • […] Kendra Little would like a few minutes of your time: […]

    Reply
  • Hello Kendra Little,

    We have aproximately 300 database servers with a total database size of 160TB and we would like to monitor all our SQL Server databases with a tool that won’t bring additional load on servers.

    We are considering Foglight for Cross-Platform Databases but also SolarWinds DPA tool.

    The main issue we are facing with our current tool IDERA is that it brings additional load on the critical servers containing databases for our banking applications and causes slowness in performance.

    In this regard, which tool do you advise for monitoring performance of SQL Server databases?

    Have a nice day and thanks in advance

    Reply
    • Apologies for the delay in responding, I didn’t catch this comment when it first came in. Disclaimer: I currently work for a company that sells a monitoring tool. I don’t feel like that influences my answer much, but just being clear. 🙂

      For any monitoring tool, whether one you are purchasing from a vendor or writing yourself, there is going to be some overhead. In part, that’s just because you need to query/poll the monitored database and record the information in an external repository, so that the monitoring can still work if the database/ instance / server is unavailable or so bogged down that it can’t respond. That means that the monitoring tool needs to do things like poll perf counters, and query SQL Server dynamic management views. The more current / responsive you want the monitoring tool to be, the more frequently it will need to poll. The more detail you want about things for performance troubleshooting like execution plans or wait stats, the more information they will need to pull.

      SQL Server is a quite mature database product, and vendors have been working in the monitoring space for years, so they are aware of this and try to strike a balance between the amount of polling they do against the instance and limiting the impact that polling the instance has. But this is an issue for EVERY vendor in the space, and there’s not really a way around it.

      If you do find a case where you believe monitoring is causing slowness, my first advice would be to work with the vendor and make sure that you’ve identified the root cause and reported it to them. They may have an adjustment they recommend you take. When evaluating other vendors, I do recommend first evaluating in a non-production environment, but then also evaluating in an environment with real load on it so you can get a sense of what the impact of the tool is, and also of course whether the features they offer fit your needs.

      Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Menu