Page History
...
- Optimal Performance Guidelines
- Monitoring the Operating System and Database
- Backup Policy
- Database Maintenance
- Index Maintenance
- Table Maintenance
- Shrink Database/Data Files
- Query Optimizer Statistics
...
- Monitor the IIS service and the CardioLog services (CardioLog Scheduling Service and CardioLog Diagnostics Service).
- Monitor the server CPU performance and memory usage.
- Monitor the logs directory size on the CardioLog server (log files . Log file growth is restricted to 8MB each).
- Monitor the database size − a rough growth estimation is typically 5GB of storage per 1,000,000 page views. See the database sizing formula in order to allocate enough storage.
- Monitor the SQL database services.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
- The CardioLog database is updated on a daily basis. The database recovery model should be set to "simple" due to its update behavior. Do not change the CardioLog recovery model.
- A full database backup should be taken before the nightly processes run (verify the nightly processing schedule). In order to backup the CardioLog database, schedule the following command:
...
It is the customer's responsibility to keep the CardioLog database backup in a safe location. For more information about the database backup procedure please consult your local DBA or Intlock support.
| Anchor | ||||
|---|---|---|---|---|
|
Backup the CardioLog installation directory after every software update.
...