Foglight for Databases is used for database monitoring across all SQL servers and Oracle databases. The monitoring covers database health, deadlocks, long-running queries, disk space usage, historical usage of active sessions, data growth, log file growth, cluster health, and CPU memory metrics. Foglight for Databases provides both real-time data and historical views. The real-time activity data is used for alerts and historical data is reviewed for trend analysis. Alerts have been set up in Foglight for Databases for long-running queries and blocking sessions. The tool is used to check for intensive database queries, including resource and CPU-intensive queries, to identify which queries are causing high CPU, wait times, or high memory usage. When the application team reports that a job is running slow, I monitor the job or query from Foglight for Databases to determine where it is getting stuck or why it is performing poorly. I can check for missing indexes and review the execution plan. If missing indexes are identified, they can be created to improve performance. The tool helps significantly from a performance perspective. Issues and their root causes can be identified through the GUI mode in Foglight for Databases. Foglight for Databases enables monitoring of multiple database platforms, including Oracle and MS SQL databases. The tool is deployed solely for monitoring, using real-time monitoring and historical data views for application support and database support operations.
Global Head of Engineering for Cloud Operations at SAI Global Compliance
Real User
Top 5
Jan 7, 2025
We use Quest Foglight for Databases for production monitoring of our databases, including Postgres, Microsoft SQL Server, and MySQL. We proactively manage our customer databases that support our SaaS application.
Senior Administrator at a healthcare company with 201-500 employees
Real User
Top 20
Nov 29, 2024
We use it for monitoring SQL databases, specifically to assess database contention. Additionally, we utilize it for real-time monitoring before deploying changes to production environments.
IT engineer at a government with 1,001-5,000 employees
Real User
Top 10
Jun 16, 2024
We use Foglight for database engines and Google servers. We use it in a private cloud, our cloud provider is Google Cloud Platform. Foglight is centralized in our data center, from there, we send it to different branches and regions of the country.
We use the solution for SQL Server and auction. We have a couple of customers using it for the other case. Other customers are also extending the infrastructure monitoring from the virtualization and the storage.
Senior Engineer at a computer software company with 11-50 employees
Real User
Nov 11, 2022
A lot of things that Foglight does could be derived from DMVs and extended events. I'm going to sound like a salesperson, but I have to be a salesperson to sell the value of a product to my company. They need to understand that to answer some of the questions they ask, not having a tool like this will make my answers very speculative. As a DBA, you have to be able to answer three questions. The first is: What's happening right now? Why is the system slow or why are things not responding? That is probably the most trivial for an experienced DBA. That is where the tool's value might not be as obvious, as you can look at the sp_who or DMV and pretty much tell what's going on without having to pay money for a license for a product like Foglight. The second question is: What just happened? There could be just a couple of seconds difference between the first and second questions. But the effort to answer the second question is significantly higher because it is water under the bridge. You need some kind of monitoring solution implemented, even if it's just a basic solution where you capture a certain timeframe, so you can roll back and review what just happened. However, there will still be a significant amount of speculation because, usually, you can't afford to monitor every single metric, and there are hundreds of them. The issue could be the OS, it could be infrastructure-related, or it could be that the SQL code is not performing well because it's not written well. So the second question is significantly harder to answer, and that's where a tool like this will become very helpful. The third question is: What has been going on? That is by far the hardest question to answer without this type of tool. This is the type of question a manager might ask for the purposes of resource planning. Or a senior VP might say, "Hey, how are we doing? Can we bring on another customer? Can we sustain a 20 percent increase in workload?" I don't know how I would answer that question without having this type of solution. I work in the industry quite a bit and there is, unfortunately, a lot of misunderstanding due to a lack of a comprehensive view of infrastructure. There's no way to answer that question without getting some kind of baseline tool. Unfortunately, in most of the shops I work for, only one question is usually being answered relatively accurately, and that is "What is going on?" And it's a luxury because by the time a customer escalates an issue and it gets interpreted by support people, there's a gap. That gap could be a couple of minutes, a couple of hours, or a couple of days.
Sales & Operations Planning Manager at a retailer with 201-500 employees
Real User
Nov 2, 2022
Foglight is used by our company to monitor production and development databases. It's being used to alert us if there are any database issues, including availability and those that are server-related. We also use Foglight SQL PI (Performance Investigator) features to troubleshoot any performance issues.
Manager of Database Services at a energy/utilities company with 1,001-5,000 employees
Real User
Apr 8, 2021
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.
Database Administrator at AmTrust Financial Services, Inc.
Real User
Mar 14, 2021
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 instances of it. Two of them are current, one of them is going to get updated next week.
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 ensures that we have a dedicated monitoring tool to monitor all our store and corporate DB servers.
Database Administrator, Information Technology at a healthcare company with 1,001-5,000 employees
Real User
Dec 9, 2020
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.
Sr. Database Administrator at a sports company with 1,001-5,000 employees
Real User
Oct 29, 2020
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.
Foglight for Databases offers comprehensive monitoring with real-time activity screens and adaptive baselines. It provides a 360-degree overview and efficient UI, requiring no custom scripts, aiding in proactive issue identification and resolution before impacting end users.Foglight for Databases is a robust tool for monitoring across multiple platforms, including SQL and Oracle. It provides features like the "Morning Coffee" dashboard and SQL Performance Investigator, enabling effective...
Foglight for Databases is used for database monitoring across all SQL servers and Oracle databases. The monitoring covers database health, deadlocks, long-running queries, disk space usage, historical usage of active sessions, data growth, log file growth, cluster health, and CPU memory metrics. Foglight for Databases provides both real-time data and historical views. The real-time activity data is used for alerts and historical data is reviewed for trend analysis. Alerts have been set up in Foglight for Databases for long-running queries and blocking sessions. The tool is used to check for intensive database queries, including resource and CPU-intensive queries, to identify which queries are causing high CPU, wait times, or high memory usage. When the application team reports that a job is running slow, I monitor the job or query from Foglight for Databases to determine where it is getting stuck or why it is performing poorly. I can check for missing indexes and review the execution plan. If missing indexes are identified, they can be created to improve performance. The tool helps significantly from a performance perspective. Issues and their root causes can be identified through the GUI mode in Foglight for Databases. Foglight for Databases enables monitoring of multiple database platforms, including Oracle and MS SQL databases. The tool is deployed solely for monitoring, using real-time monitoring and historical data views for application support and database support operations.
I primarily use the solution for database monitoring, specifically for Oracle, Microsoft SQL Server, Postgres, SAP HANA, and AWS Redshift.
We use Quest Foglight for Databases for production monitoring of our databases, including Postgres, Microsoft SQL Server, and MySQL. We proactively manage our customer databases that support our SaaS application.
We use it for monitoring SQL databases, specifically to assess database contention. Additionally, we utilize it for real-time monitoring before deploying changes to production environments.
We use Foglight for database engines and Google servers. We use it in a private cloud, our cloud provider is Google Cloud Platform. Foglight is centralized in our data center, from there, we send it to different branches and regions of the country.
We use the solution for SQL Server and auction. We have a couple of customers using it for the other case. Other customers are also extending the infrastructure monitoring from the virtualization and the storage.
A lot of things that Foglight does could be derived from DMVs and extended events. I'm going to sound like a salesperson, but I have to be a salesperson to sell the value of a product to my company. They need to understand that to answer some of the questions they ask, not having a tool like this will make my answers very speculative. As a DBA, you have to be able to answer three questions. The first is: What's happening right now? Why is the system slow or why are things not responding? That is probably the most trivial for an experienced DBA. That is where the tool's value might not be as obvious, as you can look at the sp_who or DMV and pretty much tell what's going on without having to pay money for a license for a product like Foglight. The second question is: What just happened? There could be just a couple of seconds difference between the first and second questions. But the effort to answer the second question is significantly higher because it is water under the bridge. You need some kind of monitoring solution implemented, even if it's just a basic solution where you capture a certain timeframe, so you can roll back and review what just happened. However, there will still be a significant amount of speculation because, usually, you can't afford to monitor every single metric, and there are hundreds of them. The issue could be the OS, it could be infrastructure-related, or it could be that the SQL code is not performing well because it's not written well. So the second question is significantly harder to answer, and that's where a tool like this will become very helpful. The third question is: What has been going on? That is by far the hardest question to answer without this type of tool. This is the type of question a manager might ask for the purposes of resource planning. Or a senior VP might say, "Hey, how are we doing? Can we bring on another customer? Can we sustain a 20 percent increase in workload?" I don't know how I would answer that question without having this type of solution. I work in the industry quite a bit and there is, unfortunately, a lot of misunderstanding due to a lack of a comprehensive view of infrastructure. There's no way to answer that question without getting some kind of baseline tool. Unfortunately, in most of the shops I work for, only one question is usually being answered relatively accurately, and that is "What is going on?" And it's a luxury because by the time a customer escalates an issue and it gets interpreted by support people, there's a gap. That gap could be a couple of minutes, a couple of hours, or a couple of days.
Foglight is used by our company to monitor production and development databases. It's being used to alert us if there are any database issues, including availability and those that are server-related. We also use Foglight SQL PI (Performance Investigator) features to troubleshoot any performance issues.
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.
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 instances of it. Two of them are current, one of them is going to get updated next week.
Primarily, we use it to monitor about 1,500 databases for availability and for database space, among other metrics.
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 ensures that we have a dedicated monitoring tool to monitor all our store and corporate DB servers.
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.
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.
I used it when working for a client, in a situation where you takeover management of the systems.