We use it mainly for monitoring, including CPU, memory, and disk space, and for troubleshooting purposes.

IDERA SQL Diagnostic Manager is actually for monitoring a database, that is, the CPU and memory usage. It is used for database tuning and for checking the data.

We use it to look at the overarching environment and, from there, we're able to pick and choose which servers and databases we want to view more closely. We manage over 300 servers, and 14,000 databases. We're constantly in the tool, utilizing it to drill down and determine what is going on with a specific database and query, or cache, etc.

Our primary use case is monitoring. We use the solution to get an overview of our entire environment and then drill down to view details. We look for issues that have happened in the past, that have been reported by users. We can then see what was going on, on the server, at that time, to cause such issues.

The only people who are using it are eight DBAs.

We did increase usage for lower environments rather than just production environments.

We use it to look at performance.

We use SQL DM to monitor and alert on our mission critical instances in real-time on a 24/7 basis. SQL DM was also used to troubleshoot deadlocks, blocking, and slow query performance helping in faster resolution and consistent uptime.