Quest Foglight for Databases Overview

Quest Foglight for Databases is the #2 ranked solution in our list of top Database Development and Management tools. It is most often compared to Quest Spotlight: Quest Foglight for Databases vs Quest Spotlight

What is Quest Foglight for Databases?

Foglight identifies and resolves performance issues across your applications, databases and virtual environments. The Foglight family of products easily integrates with your existing tools, so you can monitor and analyze data from almost any source across your infrastructure and view it through a single interface with our customizable, unified monitoring platform

Quest Foglight for Databases Buyer's Guide

Download the Quest Foglight for Databases Buyer's Guide including reviews and more. Updated: July 2021

Quest Foglight for Databases Customers

CommitDBA

Quest Foglight for Databases Video

Pricing Advice

What users are saying about Quest Foglight for Databases pricing:
  • "Compared to the other tools on the market, Foglight is okay in terms of pricing and licensing."
  • "It is cost-effective. With our EA, it is really based on the scale of our database environment. We found the Quest team to be reasonable and flexible when it comes to pricing and scaling of licenses."
  • "The price is worth it, if you have the time to go through the information."

Filter Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
John Waclawski
Database Administrator at AmTrust Financial Services, Inc.
Real User
Top 5
Helps us eliminate the database as the source of an issue and saves us time in finding root cause

What is our primary use case?

We use it as a monitoring tool, which is what it's designed for. And we generally only scratch the surface of it. We use it for checking blocking and locking deadlocks, server activity, database activity, running baselines, et cetera. We don't constantly look at it; we only look at it if we've noticed a problem. It could be something that might be brought to our attention where a particular database might not be running as fast as it should. The first thing we jump into is fog Foglight to see if anything jumps out at us. We have it running locally inside our server room and have three… more »

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

Don't be afraid of the interface, because you can't break anything. Click on absolutely anything and everything you can find. That's how I learned it. I took a good two or three weeks, once we did implement this. Anytime I could click on something, I was clicking on it just to see where it was going to take me. I would jot some notes down to tell me, "This took me here, that took me there." Don't be afraid to click on something. If my mouse will click on it, then I'll click on it. If anything, it's going to give me some information that I might not have had before. And if it leads me down a…
Vinothsingh Elumalai
Lead Software Engineer at Lowe's Companies
Real User
Top 5
Really helpful for assessing database performance, but we have had issues with the stability

What is our primary use case?

We are using version 5.9.5 as well as 5.9.7. Ours is a huge database infra so we are using two different environments to monitor our corporate and store servers. We have thousands of DB servers that have to be monitored across our environment, which includes Lowe's stores across the U.S. We support the infra and the monitoring for all the stores and the store-related applications, as well as the servers which support those applications. With the DB servers being an integral part of all those applications, we thought we should have a separate monitoring tool just to monitor them. Foglight… more »

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

We have had a lot of stability issues since we brought in Foglight to Lowe's. From the stability standpoint, Foglight really has to work and improve. I know that Foglight is capable of monitoring OS parameters as well as cloud DB instances, but we're not really using those features. We're just using Foglight to monitor the DB infra, purely from the database metric standpoint. The time it saves us when it comes to a root cause analysis differs from case to case. There are instances where the metrics that we are monitoring on the DB servers have really helped us to narrow down the root cause…
Learn what your peers think about Quest Foglight for Databases. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
522,946 professionals have used our research since 2012.
Anthony Nicoletti
Database Administrator, Information Technology at a healthcare company with 1,001-5,000 employees
Real User
Top 5
Tells me, from the ground up, what's going on and when, and enables me to do much more than I could otherwise

What is our primary use case?

We use it to monitor about 500 instances, 500 servers, and it keeps up with everything. I monitor Foglight. I wake up in the morning and it's the first thing I look at, because I can depend on it. We have it on VMs in-house and it performs very well.

Pros and Cons

  • "Foglight's Change Tracking capabilities are another huge feature. It is wonderful to be able to do that. People don't realize the amount of information that Foglight gathers from a given server or instance. It gets down to the version of SQL, the disk array, everything that's there. Any change that's made, any upgrade to SQL, shows up on the dashboard almost immediately. You don't know how much time you save just having a tool in your back pocket that does that for you."
  • "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."

What other advice do I have?

The biggest thing I've learned from using it is the reduction in effort that is required to do my job. Don't tell my boss that. My advice is "buy it." You won't know until you use it. I've been a DBA for 22 years and it really is an awesome tool. We use Foglight to display the most intensive database queries, but it's on a per-server, per-instance basis. We haven't created a dashboard for that, although we probably should. I can drill down into a server and I can tell you, from top to bottom, which queries are the most expensive. It could help us to improve query efficiency but we don't use it…
CL
Manager of Database Services at a energy/utilities company with 1,001-5,000 employees
Real User
Top 20
Enables us to drill down and see what is causing an issue

What is our primary use case?

We are using Foglight to monitor both SQL Server and Oracle Databases across the enterprise and across multiple directory domains. Our Foglight installation is on-premises and on virtual servers.

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

Foglight allows you to go in, modify, or create custom rules. As a user of Foglight, when you create rules and dashboards, it is important to document them. If you are not careful about coming up with proper naming standards and documentation for anything custom that you create on top of what comes out-of-the-box, then when you have staff turnover over time and you are trying to go back and understand how things were configured, it becomes challenging. Each environment is different. Different companies have different use cases. Understand your requirements and your use case. That is the key…
Kenneth Slate
Sr. Database Administrator at a sports company with 1,001-5,000 employees
Real User
Top 5Leaderboard
Performance Investigator module enables us to dig into issues and resolve them much faster

What is our primary use case?

We monitor quite a few database servers. The actual number jumps up and down on a regular basis, but on average we're doing 120 servers at a time. It gives us one pane of glass to be able to see which ones are having actual issues and which ones are just going along.

Pros and Cons

  • "The PI module allows [my colleague] to identify which new indexes or modified indexes are going to make the biggest impact."
  • "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."

What other advice do I have?

If you've got the time for it, the time to focus on databases in general, then Foglight is definitely worth the expense because of the information that it can provide for you. The biggest lesson I have learned from using this solution is that it's worth it. It enables you to pin down troubleshooting within 30 minutes to an hour, whereas before, you'd be pouring over reports or data from queries for days. That's huge. The CIO has told me that since we've started using Foglight, we've actually gotten ahead of some of these issues and we're actually being proactive instead of reactive. We're in…
MM
Senior Engineer at a financial services firm with 5,001-10,000 employees
Real User
Top 20
Enables us to monitor multiple database platforms, and our DBAs have all the information they need assembled in one place

What is our primary use case?

Primarily, we use it to monitor about 1,500 databases for availability and for database space, among other metrics.

Pros and Cons

  • "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."
  • "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."

What other advice do I have?

It's a great product. It's probably one of the best in this class and people should not hesitate getting on board with the product. I have found it's very useful for my DBAs. There are certain situations where you actually need professional services, rather than going in there and getting yourself mired up in something that you can't fix yourself. You should really consider the use of professional services before you get involved in problems that you can't fix yourself.