Page History

Maintaining a well organized system aids in speed and performance.

Contents

• Optimal Performance Guidelines
• Monitoring the Operating System and Database
• Backup Policy
• Database Backup
• Application Backup
• Database Maintenance
• Index Maintenance
• Table Maintenance
• Shrink Database/Data Files
• Query Optimizer Statistics

Optimal Performance Guidelines

...

1. Install the CardioLog application and database on dedicated servers that meet or exceed the recommended hardware and software requirements.
2. Upgrade the product to the the latest version. To find out what is your product version, go to Administration > Product License.
3. Monitor the operating system and database.
4. Schedule all CardioLog service jobs to execute off-peak hours, while no other system job is running (for example: system backup, SharePoint search crawl etc.). By default all CardioLog service jobs are scheduled to run every day at midnight, except Usage Data Processing which runs every hour.
5. Configure email alerts for scheduled services and event collection thresholds that will be sent to the system administrator.
6. Execute this script against the CardioLog database to learn about your current database size, the amount of usage data that you have, index fragmentation rates and more.
7. Reorganize and rebuild database indexes with high fragmentation rates.
8. Archive history data to free up disk space on the database.
9. Delete unused reports and optimize existing reports. You can execute this script against the CardioLog database to retrieve a list of all reports in your system, with the following details: report path, report name, schedule type, owner, number of widgets, website item filter and date range filter. 

Anchor
monitoring monitoring

Monitoring the Operating System and Database

1. Monitor the IIS service and the CardioLog services (CardioLog Scheduling Service and CardioLog Diagnostics Service).
2. Monitor the server performance (CPU and memory usage).
3. Monitor the Logs directory size (log files growth is restricted to 8MB each).
4. Monitor the database size - a rough growth estimation is 5GB of storage per 1,000,000 page views. See the database sizing formula in order to allocate enough storage.
5. Monitor the SQL database services.

...