The database layout was completely redesigned starting in version 2.50 to resolve slow query times when using the web reports. The new EventSentry database tables and indexes were designed to accommodate large amounts of data while still providing fast query responses.
When you expect large amounts of data (e.g. more than 1 million records) it is however still important that you take steps to ensure that the database is optimized at all times. Below you will find recommendations for various supported databases when you expect to collect large amounts of data.
Microsoft SQL Server®
|1.||When creating the database, make sure that you set the initial database size sufficiently high. This will improve the overall performance because the database engine will not have to continuously extend the data files. This applies to both the data files and the transaction log size. In addition, configure the file growth rate larger rather than smaller. The screenshots below show a good starting point for potentially large databases:|
|2.||Reorganize the tables on a regular basis, but especially after you purge or move old records. SQL Server offers a feature called Maintenance Plan that lets you schedule a database maintenance on a regular basis or by demand. Keep in mind that a database reorganization can temporarily use more disk space, so always make sure that you have enough disk space for the database and transaction log available. The maintenance plan wizard can be launched by right-clicking the database and choosing "Maintenance Plan" from the "All Tasks" submenu. The screenshot below shows a recommended configuration.|