The SQL Sentry client, monitoring service, and database are typically installed as follows:
- The SQL Sentry database is installed on a SQL Server instance on your network.
- The SQL Sentry client is installed on your workstation computer(s) with network connectivity to the SQL Sentry database.
- The SQL Sentry monitoring service is a Windows service and is installed on a dedicated server or VM with network connectivity to the SQL Sentry database server and monitored targets.
- For monitoring cloud targets, the SQL Sentry monitoring service may be installed either on-premises, or on a Windows virtual machine (IaaS) in the respective cloud platform.
- The SQL Sentry portal service is part of the optional SQL Sentry Portal feature that may be installed. It can be installed on a machine along with the SQL Sentry monitoring service and SQL Sentry client, or it can be installed on a machine by itself without any other SQL Sentry components (recommended).
- If you are using the EPI version of SQL Sentry, then it must be installed on a machine that has the SQL Sentry controller service.
The SQL Sentry clients and monitoring services are each configured to connect to the same SQL Sentry database during setup.
High disk latency (>5ms per read IO avg, >1-2ms per write IO avg) can limit scalability and cause sluggishness with the SQL Sentry client. The greater the number of monitored targets, the more data is collected and stored in the SQL Sentry database, and the more fast storage becomes important. Modern flash or hybrid storage systems should be used for maximum scalability and performance.
You should always monitor the SQL Sentry database with SQL Sentry to ensure there are no CPU, memory, or disk bottlenecks. A free license is included in every SQL Sentry installation for this purpose. Simply add the SQL Server as a monitored target.
Install the SQL Sentry client, monitoring service, and database on the same network for the best performance. For example, if the SQL Sentry client or monitoring service connect to a SQL Sentry database over a slow wide area network link or VPN over the internet, performance may suffer.
If a slow connection from your workstation to the SQL Sentry database is unavoidable, it is recommended to install the SQL Sentry client on a “jump box” on the same network as the database, and access it via RDP or another remote desktop technology.
For smaller environments, you may want to install a monitoring service on the same SQL Server machine where the SQL Sentry database is located. Doing so minimizes network overhead for communications between the monitoring service and the database. However, bear in mind that they will share the same compute resources which may cause CPU contention. For more information, see System Requirements.
Depending on the size of your SQL Server environment, you may need to install multiple SQL Sentry clients and monitoring services. Typically, each DBA has the SQL Sentry client installed on their workstation, and enough monitoring services are installed to handle the monitored target load (see examples below).
In Azure, all the SQL Sentry components can be co-located on one IaaS VM or—to support larger numbers of monitored targets—must be set up on multiple VMs. As noted above, the SQL Sentry database may also be hosted on Azure SQL DB Managed Instance.
Consumption may increase if there are multiple sites (which we recommend mirroring to Azure Regions) and require redundancy in each site. In cases where redundancy is required, we recommend an N+1 approach with monitoring service VMs as described in the implementation examples (below). If you want to have a cluster for the SQL Sentry database for redundancy, that will also increase consumption.
In the SQL Sentry database implementation examples (below), the storage setup on the database is for two disks. One OS disk at 32 GB, and one data disk at an additional size dependent on workload. Unless workload demands moving TempDB to its own persistent disk, use the temp local disk.
- For the SQL Sentry database, you can constrain the CPU count on the deployed system to reduce license cost for SQL Server. See the Azure Constrained vCPU Capable VM Sizes article from Microsoft for details.
- The storage estimates in the implementation examples (below) are simplified to request one managed disk of the size needed for data, but additional throughput and performance can be obtained by using multiple smaller disks as necessary. See the Performance Guidelines for SQL Server in Azure Virtual Machines article from Microsoft for more information.
- For more information about Azure consumption costs, please see the Azure Pricing Calculator from Microsoft.
The SQL Sentry Scalability Pack implements partitioned clustered columnstore indexing, In-memory OLTP, and additional optimizations to achieve maximum scalability and performance, with reduced CPU, memory, and disk requirements. Contact us at support.solarwinds.com to schedule pack installation, which is free of charge. For more details, see the SentryOne & Microsoft Achieve SQL Server Monitoring Performance Goals blog post.
Multiple monitoring services can be installed to handle more than 100 monitored targets, and/or to provide automatic redundancy and load balancing. There is no configuration required to implement a basic SQL Sentry cluster.
If increased fault tolerance is required for the SQL Sentry database, install the database on a clustered SQL Server instance.
Important: Due to performance considerations, we do not support Synchronous-commit mode for the Availability Group hosting the SQL Sentry database when monitoring over 200 targets or over high latency network links.
We recommend using Asynchronous-commit mode in this scenario.
See the following blogs from Microsoft for more information on this topic:
Implementation Examples - Estimates Only
|Number of Monitoring Services||Maximum Number of Monitored Targets Range|
Each monitoring service requires a dedicated Windows server or VM with these minimum hardware specifications:
|CPU||RAM||Azure VM||EC2 Class|
|4 cores 2.0+ GHz||12 GB||Standard_D4_v3 (4 cores (2.0+ GHz), 16 GB RAM)
Standard SSD, E4: 32 GiB, single disk
Important: The actual number of services needed to optimally monitor an environment is heavily dependent on several factors such as:
- The number of databases on each target
- The number of disks on each target
- The workload on each target
- Geographical placement of datacenters
- The number of domains and the trust between those domains
SQL Sentry has settings to limit the maximum number of disks, databases, database files, and indexes to collect for each target, and these can be easily adjusted as needed. The SolarWinds support team (support.solarwinds.com) will work with you to ensure optimal configuration and performance.
|Number of Targets||Minimum Specs||Recommended Specs|
Note: The EC2 DB Instance Class Types, Azure VMs, and Azure SQL Managed Instance recommendations are provided as examples. Please see:
- The AWS DB Instance Class documentation for the latest EC2 types and specifications available
- vCore model overview - Azure SQL Database and Azure SQL Managed Instance for the latest Azure VM and Azure SQL Managed Instance offerings available
The estimates provided are based on the default configuration of SQL Sentry. The hardware and resources needed by the SQL Sentry database to handle a monitored environment is heavily dependent on factors such as:
- The query workload
- Retention settings
- Collection interval settings