Using it was just a security process that had to be done. We didn't change the way we were working or the way things are working. It's just an additional process that makes sure everything is secured. It didn't change anything in our environment. It was just a need, and the product does exactly what we needed.

The tool can track logins and login failures. I made my own alert so that if there is a certain number of login failures for a server, it emails me. That is really useful. If I want logins to automatically lock out after a certain number of failed attempts, I can know when that happens. It's a good security feature but it also helps because sometimes users are setting up their report or their service and they lock out their account but they don't tell anyone. I can easily see that.

It's really useful because, with over 100 servers, it's difficult to check that many. It's nice to have Idera where it clicks everything into central Repository, a central server, and you can just query that.

The big requirement of our audit is to track logins and SQL Compliance Manager centralizes it, puts it in a spot where we can "protect" the logs. It's not like logs on the server that could be wiped out. It's collected centrally and we can lock that down.

It provides our Internal Audit team with a tool to use for SOX compliance.

I can't really give an example of how the product has improved the way our organization functions as a whole, but for me, personally, a few years ago, it helped me diagnose a problem that we were having on one of our servers. It helped answer a question, which was nice.