RockSolid SQL Managed Services

Monitoring

RockSolid captures all data from SQL Server that is relevant from a performance, security, recoverability, configuration, optimization or management perspective. And RockSolid does this in a way which is low impact allowing monitoring to be “always on”.

Get Started

SQL Server Monitoring

End to end SQL Server database monitoring. Collection of data covering configuration, operations, security, capacity, performance and management in real time. Auto discovery of HA, DR and replication scenarios.

Operating System (OSE) Monitoring

Monitoring of all operating system resources and events that related to database operations and performance. This includes virtual/physical resources such as CPU, Memory, capacity, process, disk throughput and network throughput.

SQL Server Instance Discovery

Discovery of deployments of SQL Server within your environment. Uses a combination of techniques to both passively listen for SQL Server instances, but also actively inventory hosts across sites and domains to discover SQL Server installations.

No Installaion on Target Hosts

RockSolid uses a central network agent deployment topology which does not require installation on the hosts being monitored. This provides an easy, rapid and low risk rollout of RockSolid to large fleets of database servers.

Real-time Data Centralisation

RockSolid centralises monitoring data into a central RockSolid repository in real-time. This allows for robust analysis and reporting to be driven directly from the RockSolid repository across all hosts, regardless of target host network location.

Designed for Complex Networks

RockSolid is designed and used in some of the most secure and complex network environments. RockSolid copes with multiple domains, network segments, multiple geographies, WANs and hosts firewalled hosts.

RockSolid captures all data from SQL Server that is relevant from a performance, security, recoverability, configuration, optimization or management perspective. And RockSolid does this in a way which is low impact allowing monitoring to be “always on”.

RockSolid’s monitoring is scalable from small numbers of instances to thousands of production SQL Server installations. In all configurations RockSolid maintains a single data repository allowing high quality reporting and ad-hoc analysis to occur.

The following data is monitored by RockSolid:

Configuration

  • Version & Build
  • Edition
  • Processor count
  • Processor Family
  • Collation
  • Cluster nodes
  • License configuration
  • OS version/build
  • SQL Server Configuration Values
  • Default Backup directory
  • Binaries location
  • Network libraries
  • SQL Service properties
  • Windows Services properties
  • Databases
  • Database File Groups
  • Database Data Files
  • Database Data File Space Details
  • Windows Disks
  • Disk File System
  • Disk Compression
  • Disk Space/Free
  • Windows Mount Points
  • SQL Agent Jobs
  • SQL Agent Job Schedules
  • SQL Agent Job Steps
  • SQL Agent Job Execution History
  • SQL Agent Job Step Execution History
  • Replication Publishers
  • Replication Subscribers
  • Replication Latency (perfmon)
  • SQL Server Error Log
  • SQL Agent Error Log
  • Windows Error Log (filtered)
  • SQL Error Log size
  • SQL Agent Error Log size
  • Database Backup History
  • Database Restore History
  • Database Tables
  • Database Indexes
  • Database Stored Procedure Checksums
  • Replication Latency (tracer token)
  • Database Function Checksums

Recoverability

  • Database Backup History
  • Database Filegroup Backup History
  • Database Data File Backup History
  • Differential Backup History
  • Database Log Backup History
  • Database Backup File Retention
  • Database Backup File Archive Status
  • Database Restore History
  • Database Log Shipping Configuration
  • Log Shipping Latency
  • Database Mirroring Configuration
  • Database Mirroring Latency
  • Database Snapshots

Security

  • SQL Server Service Account
  • Database Role Memberships
  • Database Users
  • Object Level Permissions
  • Application Role Memberships
  • SQL Server Logins
  • SQL Login Password Stats
  • Windows Group Enumeration
  • Server Role Membership
  • Database Schemas
  • Encryption Keys Details
  • Certificate Details
  • Endpoint Configurations
  • All administrative queries
  • Database Schemas
  • Encryption Keys Details
  • Certificate Details
  • Endpoint Configurations
  • Audit Log Specifications
  • Audit Log Stats
  • Audit Log Status

Availability

  • Connection Availability Test
  • Basic Query Execution Test
  • Database Availability Test
  • Instance Down
  • Instance Started Event
  • Cluster Node Location
  • Instance Stability (reoccurring restarts)
  • Job Failures through Node Failures

Performance

  • Long running transactions
  • Instance logout events
  • SQL Server Wait Stats
  • Database virtual file stats
  • SQL Server Connection Counts
  • SQL Server Internal Memory Allocations
  • Index Fragmentation Statistics
  • Database Table Row Counts
  • Database Blocking Information
  • Blocking query details
  • Blocked query details
  • Query Deadlock Graphs
  • Long Running Transactions
  • Missing indexes
  • Unused indexes
  • Index operational stats
  • Stored Procedure Execution Stats
  • Memory Grant Stats
  • Query Optimizer Execution Stats
  • Query Memory Semaphore Stats
  • Query Execution Stats
  • Resource Governor Stats

Always On Monitoring

We understand that in some environments DBAs may not have detailed knowledge of every system. This means that when an issue is logged, they may not have an understanding for how the system is “different” from its norm. RockSolid helps to mitigate the impact of this by providing always on monitoring. This simply means that monitoring has been designed to be on for production systems under normal circumstances. This is true even when the site has hundreds, or thousands of databases.

In addition to monitoring always being on, that data collected from monitoring is intended to be kept long term. Typically, 365 days or more.

Monitored Data Retention

RockSolid maintains a single data repository per installation. This repository may be used to house the data from many different sites and domains. While the size of the repository will vary based on the number of instances being monitored, key data aggregation techniques are used to ensure the size of the repository don’t become excessive.


Aggregated Data Example

This example shows how a set of data is aggregated after a period of time. But when the aggregation occurs, RockSolid does it in a way to avoid losing the relevant data detail. This ensures that the aggregated data remains usable for performance comparisons long term but also does not consume excessive disk space.

RockSolid Repository Size

The size of the central RockSolid data repository will vary based on the number of instances monitored by RockSolid. RockSolid however performs a number of tasks to ensure the size of the central repository remains manageable. These tasks include:

  • Smart data aggregation
  • Automatic data archive
  • Text Data compression
  • Data retention configurable as part of policy

While it may not be necessarily indicative of your site, the following example provides details of the RockSolid data repository size for a real world implementation. This implementation monitors over 200 production instances and has 365 days of data retention.


Example RockSolid Repository Size

Network Impact

The RockSolid Agent is designed to be deployed on a network close to the SQL Server – i.e. LAN connectivity. This is to ensure good connectivity for the purpose of monitoring availability and for the purpose of collection of data, such as performance data.

The RockSolid Agent however can be remote from the central RockSolid Server. The RockSolid Agent does not assume reliable and/or high speed connectivity back to the RockSolid Server. In addition, the RockSolid agent carries out data reduction activities such as compression and data de-duplication. This ensures that traffic from the RockSolid Agent to the RockSolid Sever is minimal.

SQL Server Impact

RockSolid is designed to collect a lot of detailed data continuously from SQL Server. However we have designed this to be low impact on the SQL Server instance being monitored itself. While results vary RockSolid is not expected to add more than a small background load onto the SQL Server and in general RockSolid will have no significant impact on the performance of the SQL Server instance.

RockSolid now monitors thousands of production instances including SQL Server instances processing many thousands of transactions per second. RockSolid collects detailed data from all of these instances continuously and has not caused any form of significant overhead.

seperator

 

Get Started

Provide some details and we'll provide a quick quote so you can assess the level of savings possible in your environment.

First Name: Last Name:
   
Company:
 
Email:
   
Phone:
 
How many SQL Servers are in your Environment?: