We performed a comparison between IDERA ER/Studio and Quest Foglight for Databases based on real PeerSpot user reviews.
Find out in this report how the two Database Development and Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Developing new dimensional models; for the data we're hosting, dimensional modeling is more useful."
"The most valuable features are... those that enable me to represent the database to the development community and the business users."
"The most important features are logical and physical models that we can compare and develop. Also, the Data Dictionary can be created out of your studio. Finally, database schemas help understand the logic that's behind the scene, behind the SQL tables. Especially when there are a lot of them, the schemas help everyone understand the business processes."
"We are able to document the data lineage and data flows of our data from one system to another."
"IDERA keeps up with the versions of Oracle and SQL Server that I'm using. I mostly use SQL Server and when there are new features, a new type of index, for example, IDERA also includes them in upgrades of the data modeling tool."
"Using this product has improved the way we maintain our models because they have a place where we can keep all of them, and they can be viewed using the web interface."
"The data modeling module is important to me because I am a database developer and designer... It's very fast, reliable, up-to-date, so easy to use, smooth."
"The most valuable feature of the solution is generating DDL (data definition language)."
"The real-time activity screens are also helpful... if there is something that is running slowly, we can eliminate the database as being an issue and perhaps look at the server, network activity, or something outside of the realm of the database as being the issue."
"We can visualize all the different types of DB servers that we are monitoring in a single pane of glass. It uses a 360-degree overview of the database, for each of those databases that we are monitoring. That includes what kind of resource utilization is happening and what kind of DB parameters are getting monitored, as well as the different types of DB parameters that are being offered for each database type."
"One of the hardest things to do in database management is to evaluate performance deviation across time. The adaptive baseline that Quest is using is by far the most helpful. That doesn't necessarily mean I use it on a daily basis, but it is something that I have not been able to find in any other tool, at the same level."
"The PI module allows [my colleague] to identify which new indexes or modified indexes are going to make the biggest impact."
"Foglight is also able to help the DBAs proactively fix problems before they become an issue. It provides them with real-time activity screens that help in this regard. The DBAs are able to go to these screens and look at what's happening in real time, and that buys them time. It helps them see problems ahead of time and find solutions to them."
"The alarms alert proactively if there are any potential or ongoing issues with the databases that we support. That means we can take preventive or corrective action before the issue becomes a big issue. And the SQL PI features enable us to drill down into performance issues in our databases so that we can improve performance, which is important."
"The ability to monitor multiple database platforms streamlines our database operations. The single pane of glass is what we were really after when we picked Foglight. We knew we wanted something that could monitor cross-platform because it does save a lot of time to use the same tool. The one thing that I like with Foglight is that we don't have to install anything locally, like agents, directly on the database servers. That was also a big seller because it simplifies things."
"Its reporting capabilities are immense."
"Whenever there is a new version, there are a lot of release notes on the technical side of it, but I would like to be told why are we doing the upgrade... What I would like to really see is how this benefits us from the business point of view. What are the real benefits that the user gets? I want some kind of way white paper. The release notes describe the technical enhancements but, from the layman's point of view, if someone asks me what are the business benefits of this upgrade, I don't have any documentation to explain it to the business."
"We would always like to see Repository performance improve, checking in and checking out."
"The solution could be sped up, as it is a little slow (e.g., when it's doing its database compare)."
"This solution needs more precise documentation."
"I would like to upload, a database with about 3,000 tables. It takes so much time and, finally, it freezes the whole solution so that I actually cannot work with that environment. For the data warehouse, it's fine because I have 20 or 30 tables. It works fine. But, when I reverse-engineer the database with 3,000 tables, it freezes and it's hard to upload and reverse-engineer such environments in ER/Studio."
"When building the relationships there should be a little more flexibility."
"It would be helpful if they could create a generic JSON database type, as a target database, rather than a specific one like Mongo."
"What I would like to see improved is the reliability of the releases, releases that are a little less buggy."
"I would like the rule development code to be made available so we don't always have to be referred to professional services for custom solutions. For example, if we want to exclude certain databases from a particular rule, we shouldn't have to go to support and to professional services for that solution. If the code and syntax were available, we have resources that could quickly turn something like that around."
"The system is not that stable. We have been facing a lot of issues. We built a new store environment of Foglight, an environment for monitoring the Lowe's store servers, which are all Db2 servers. The objective is to monitor 800 Db2 servers in each Foglight instance. Up to 150 Db2 servers, the environment was working fine. The moment it crossed 150 or 160, we started having a lot of stability issues."
"When holding data for two years for 20 SQL Servers, the reporting becomes sluggish and unresponsive."
"The data model needs improvement when it comes to creating custom reports. That is an area where it needs a bit of improvement. Foglight gathers a lot of information around our databases as part of its monitoring. While I know all this information is in there, trying to pull the metric we want out for custom reports is sometimes hard to find. One nice thing about Foglight is that you can create custom dashboards, which you can easily convert to reports. We would be doing a lot more of that if it weren't for the challenging data model."
"One thing that I would like, and it's probably something that I could set up internally, is something other than a dashboard which I have to look at to know that a server is down. I'd like bells and whistles to go off... If I look at the dashboard I know there's a server down. But if I'm not looking at it, if I'm looking at some other problem, I want to know about it. You can do that, you can use SMSs and alerts to your phone, and I could set it up to handle that, but it would be nice if, out-of-the-box, Foglight did that."
"When we decided to go with Foglight, a lot of people stopped using the diagnostics part because it was very intimidating... They still won't use it because they feel it's too intimidating. They will open something up and not know what to do. It's not very user-friendly. You have to click on a lot of stuff to find the information."
"Foglight does have a component that allows you to look at things in real time, but it's not as friendly or as efficient in terms of responsiveness as Quest Spotlight is. Foglight might be lacking in this department."
"I get a lot of alerts that, while important, are not critical. Then I have to dig in and figure out how to turn alerts off, but not the logging. I want to be able to go back, once we get the other big issues out of the way, and start fine-tuning some of those other areas, but I don't necessarily want to receive an email for all of them."
IDERA ER/Studio is ranked 14th in Database Development and Management with 34 reviews while Quest Foglight for Databases is ranked 2nd in Database Development and Management with 10 reviews. IDERA ER/Studio is rated 8.4, while Quest Foglight for Databases is rated 8.6. The top reviewer of IDERA ER/Studio writes "The solution has important reverse engineering features, but it needs a single sign-on feature". On the other hand, the top reviewer of Quest Foglight for Databases writes "Excels at displaying intensive database queries and enables me to address things before they become real problems". IDERA ER/Studio is most compared with erwin Data Modeler by Quest, SAP PowerDesigner, Sparx Systems Enterprise Architect, Toad Data Modeler and erwin Evolve by Quest, whereas Quest Foglight for Databases is most compared with Quest Spotlight, SolarWinds Database Performance Analyzer, Oracle Enterprise Manager, IDERA SQL Diagnostic Manager for SQL Server and Redgate SQL Toolbelt. See our IDERA ER/Studio vs. Quest Foglight for Databases report.
See our list of best Database Development and Management vendors.
We monitor all Database Development and Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.