If your data_engine setting 'delete raw samples' is set too high, e.g., 365 days you may consider gradually cutting back on the size of your database as there may be too much data for the data_engine maintenance to complete in a timely fashion and not cause DB problems. Normally customers save 90 days or so of raw data unless there is some business reason to save more data. Due to this setting data_engine maintenance can take taking a long time.
Partitioning of Raw Sample Data (SQL Server)
Important! When using the Partitioning feature, schedule maintenance to run daily.The time required to execute the partitioning depends on amount of data as well as performance of disk subsystem but can for large installations take several hours or even up to several days.
The sample data tables can be partitioned in order to achieve improved performance.
The sample data will be partitioned by day so if you for instance have configured the system to delete raw sample data older than 365 days, then the sample data tables (RN_QOS_DATA_xxxx) will each be configured with 365 partitions (plus a few extra partitions in order allow for faster maintenance).
SQL Server: If using partitioning then the property Delete raw data older than must be between 1 and 900. SQL Server, up to and including 2008 SP1, limits a table to 1000 partitions.
Partitioning will contribute to improved performance and faster more efficient maintenance when accessing the raw sample data tables:
- higher insert rates
- faster read access to data
- faster data maintenance (delete/compress of sample data)
- faster index maintenance
For complete information see:
The data_engine runs a query to determine the MS SQL Server edition and if applicable enables the table/index partition option in the data_engine.
Note that data_engine 7.91 which is part of NMS 6.50 does not recognize MS SQL Server 2012 Enterprise edition properly and does not enable the table/index partitioning option. data_engine version v7.92 fixes this issue.
This fix applies only to NMS 6.50 version of the data_engine.
DBAs can also examine the transaction log and/or use SQL profiler to see which transactions are filling up the log.
keywords: transaction log disk fill filling up error database maintenance administration space data_engine SQL Server recovery model mode simlpe full table truncate truncation data raw settings configuration ExecuteNoRecords.