If you were talking to someone whose organization is considering IDERA SQL Compliance Manager, what would you say?
How would you rate it and why? Any other tips or advice?
Plan ahead in terms of what to audit so that the Repository database doesn't get crazy big.
We've had some problems with the install so watch out for some "gotchas" there. It takes a little bit of setting up. For example, if you have privileged users you have to put them in so you don't audit what they're doing, because you don't care about that piece. So there is a little bit of setup. Be prepared for some upfront time spent with it. I rate it pretty highly, around an eight out of ten. It wouldn't be a ten, because of the install hassle that we ran into. But it's a good product, it does what we need it to do.
You should look at your use cases, the type of stuff it collects. In terms of cons, you really need to make sure you trim your data, your archive. Otherwise, depending on your activity, your database can get huge, unusable. I give this solution a nine out of 10. It's not a 10 because I have to babysit the agents. They stop collecting and I have to manually restart them.
What I like most among all IDERA products is Diagnostic Manager. It's really easy to use, it's very stable. It comes out of the box with a good threshold for certain counters. After that comes Compliance Manager. It's a nice tool as well, with some restrictions as I already mentioned. But on the whole, a very good product as well. I would rate IDERA SQL Compliance Manager at seven out of 10. I like the product, I like the features, but not everything is working as intended and development isn't as fast as I would expect. Also the bug-fixing takes too much time, in my opinion. That's why I wouldn't give it a 10.