IDERA SQL Doctor Review

By capturing performance issues when they happen, we do not miss crucial data

What is our primary use case?

It is the first action our service desk takes when a performance or stability issue arises. This way we have the crucial data waiting when the DBA comes in.

How has it helped my organization?

We have instructed our service desk to start capturing with SQL Doctor when performance issues are being called in. Therefore, we do not miss the crucial data from that specific moment. The senior analysts then can do their analyses afterwards.

What is most valuable?

  • Indexing and locking analyses
  • The ability to generate optimize scripts.
  • The prioritized recommendations are nice to have. 

Furthermore, you can have multiple scans archived when comparing the tracing from a baseline perspective. Two scans can give us insights concerning the difference between a good and a bad situation.

What needs improvement?

SQL Doctor should be improved in Availability Groups, mirroring, and clustering analyses. We mostly see index and query plan analyses. It should be broader than this.

For how long have I used the solution?

One to three years.

What other advice do I have?

It is the perfect first action that we can take with the help from our service desk!

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment