Slow application
You do not know whether the source is SQL, a query or the application itself.
Total control of SQL Server, with no impact
The most efficient way to understand and control SQL Server
Four9s is an advanced SQL Server observability platform that provides complete, real-time visibility into what is happening in your environments.
Monitor heavily loaded servers with minimal impact. It creates no traces, adds no objects to tempdb and requires no agents on monitored systems.
We also offer a mobile application and, above all, listen to our customers: their feedback helps us build new features and improve existing ones.
You know something is wrong, but not why
Does any of this sound familiar? Select a problem to discover our solution.
Difficult blocking
The blocking has disappeared and you do not have enough evidence.
What happened yesterday?
The incident is over, but you need to reconstruct what happened.
Usage spikes
CPU, activity or resource usage rises and you need to know why.
Where is the problem?
You need objective data to identify the source of an incident.
Business impact
A SQL incident can affect critical processes in your organization.
From detecting the problem to understanding its cause
Detect. Understand. Prove. Anticipate.
Continuous visibility
Know what is happening in SQL at every moment.
History and replay
Go back and analyze exactly what happened.
Data correlation
Relate SQL activity to system metrics.
Minimal impact
Monitor high-load environments without creating traces.
Objective evidence
Get the data you need to find the source of the problem.
SQL specialisation
A solution built for teams that work with SQL.
Four9s takes observability to the next level
-
Real-time monitoring: control all your SQL activity, second by second
Four9s provides real-time monitoring of your SQL Server databases, allowing you to identify and resolve performance problems quickly and efficiently.
-
History and replay: review past activity
- Review past activity as if you had been there, using second-by-second data collection.
- Find the source of blocking and the processes that caused the system degradation.
- Use Four9s incident replay to analyze the exact moment, including the time before and after the impact on the system.
-
Objects and ad hoc: usage metrics for every object and ad hoc query
- Get detailed information about current statistics stored in the SQL Server cache and how they evolve over time.
- Monitor the usage and performance of stored procedures, functions and triggers to identify significant changes.
- Analyze the causes of process degradation, compare previous and current execution plans, and identify who changed the code.
- Capture complete executions that meet specific criteria to examine their actual execution plan and understand their behavior.
-
Errors: detect application and other errors
These features give database administrators visibility into errors that may occur in SQL Server.
- Capture errors with severity 10 or higher, such as an application calling a procedure that no longer exists or using incorrect parameters.
- General SQL Server errors.
- Application timeouts when calling a stored procedure or query, including the parameters used.
-
Databases: database usage and analysis
This section provides information about disks, each database's impact on system resource usage, current sizes and growth projections.
Database details show the current size of data and indexes, the number of rows in each table and how these values evolve over time.
Drilling into a table reveals valuable information to help DBAs make decisions about index and statistics maintenance, including which database processes use them.
-
Incident management
In the Four9s incident panel you will find incidents generated according to the thresholds specified in the configuration. With one click, Four9s takes you to the exact moment when the incident was generated.
These incidents can be integrated for delivery to email, Teams, Jira, Dynatrace, Splunk and other tools.
-
Calendar: compare time ranges
Compare activity differences across time ranges to quickly discover degraded processes, including new processes that were not previously running.
Answer questions such as: Why was CPU usage 45% during this period? Why is it 45% on Saturdays at 20:00 but 25% on Mondays at the same time? Which processes or queries run more often or have degraded?
-
Reports, auditing and much more
Export reports showing the evolution of SQL Server and business counters. If you develop your business databases, auditing can save many hours when a project requires database object changes.