This section describes the required configurations as well as the optional configurations available for the Solution Package for Microsoft SQL Server in the RTView Configuration Application. You must define the classpath to the SQL Server JDBC jar file and you must also define data source connections for each SQL Server that you want to monitor.
Use the RTView Configuration Application to configure your data collection.
The Add Connection dialog displays.
Connection Name: specify the name you want to use for the connection.
Database URL: Enter the complete URL for the SQL Server.
Username: The username is used when creating the connection to the SQL Server.
Password: This password is used when creating the connection to the SQL Server. By default, the password entered is hidden. Click the icon to view the password text.
The newly created connection displays in the Connections section.
You can specify the number of history rows to store in memory, the compaction rules, the duration before metrics are expired and deleted, and the different types of metrics that you want the Historian to store in the DATA STORAGE tab in the RTView Configuration Application.
You can modify the maximum number of history rows to store in memory in the DATA STORAGE tab. The History Rows property defines the maximum number of rows to store for the MssqlServerStats and MssqlPerfCounters caches. The default settings for History Rows is 50,000. To update the default setting:
Data compaction, essentially, is taking large quantities of data and condensing it using a defined rule so that you store a reasonably sized sample of data instead of all of your data, thus preventing you from potentially overloading your database. The available fields are:
Condense Interval -- The time interval at which the cache history is condensed for the following caches: MssqlServerStats and MssqlPerfCounters. The default is 60 seconds.
Condense Raw Time -- The time span of raw data kept in the cache history table for the following caches: MssqlServerStats and MssqlPerfCounters. The default is 1200 seconds.
Compaction Rules -- This field defines the rules used to condense your historical data in the database for the following caches: MssqlServerStats and MssqlPerfCounters. By default, the columns kept in history will be aggregated by averaging rows with the following rule 1h -;1d 5m;2w 15m, which means the data from 1 hour will not be aggregated (1h - rule), the data over a period of 1 day will be aggregated every 5 minutes (1d 5m rule), and the data over a period of 2 weeks old will be aggregated every 15 minutes (2w 15m rule).
Note: When you click in the Compaction Rules field, the Copy default text to clipboard link appears, which allows you copy the default text (that appears in the field) and paste it into the field. This allows you to easily edit the string rather than creating the string from scratch.
The data for each metric is stored in a specific cache and, when the data is not updated in a certain period of time, that data will either be marked as expired or, if it has been an extended period of time, it will be deleted from the cache altogether. By default, metric data will be set to expired when the data in the cache has not been updated within 45 seconds. Also, by default, if the data has not been updated in the cache within 3600 seconds, it will be removed from the cache. The following caches are impacted by settings in the Expire Time and Delete Time fields: MssqlServerStats, MssqlServerDatabaseSizes, MssqlServerTableSizes, MssqlPerfCounters, and MssqlWaitStats. To modify these defaults:
The History Storage section allows you to select which metrics you want the Historian to store in the history database. By default, historical Server Statistics (MssqlServerStats cache) and Performance Counters (MssqlPerfCounters cache) are saved to the database. To disable the collection of this historical data, perform the following steps:
The History Table Name Prefix field allows you to define a prefix that will be added to the database table names so that the Monitor can differentiate history data between data servers when you have multiple data servers with corresponding Historians using the same solution package(s) and database. In this case, each Historian needs to save to a different table, otherwise the corresponding data server will load metrics from both Historians on startup. Once you have defined the History Table Name Prefix, you will need to create the corresponding tables in your database as follows:
Note: If you are using Oracle for your Historian Database, you must limit the History Table Name Prefix to 2 characters because Oracle does not allow table names greater than 30 characters (and the longest table name for the solution package is 28 characters).
To add the prefix: