Skip Navigation Links.

CDRv5 Client – Database Storage

image for CDRV5 client server connectivity overview
Database Storage Configuration

Use ‘Home | Database Storage’ to navigate to the database storage configuration page.

This pane is used to configure the storage duration of the main CDRv5 tables: CDR, CPM and Summary tables. The default values are CDR=90 (days), CPM=1 (day), and Summary=12 months.

The CDR table is useful to generate many type of reports including those report requiring originating numbers.

The Summary table aggregates the details using the toll-free number and the terminating number as keys. The originating number details are lost. The summary table provides faster performance and requires less disk space. Hence, the record retention period can be much longer.

The CPM table keeps call progress message and is useful for querying detailed events of calls. Most of the information is capture in the final CDR. Hence the retention requirement is generally relatively short.

When you select a storage duration, you should consider your practical needs and many factors such as:
  • Your MS-SQL product. If you use MS-SQL 2012 Express, you are limited to a storage of 10Gbytes. The longer the storage duration, the more chance to hit the limitation and causing database failures.
  • Computer storage capacity. The longer the storage duration, the more space it will require. The CDR/CPM is approximately 240 bytes. Relational Database Management System also need overhead storage. You should monitor the disk space usage of your database files. By default, these CDRv5 Database file are located under the sub-folder ‘..\CDRv5DatabaseFiles’. The filenames are ‘CDRV5Database.ldf’ and ‘CDRV5Database.ldf’.
  • Storage hardware. You may consider to store the CDRv5 Database files in fast and fail-safe drives (RAID Arrays for example).
  • Query response time and record insert rate. The longer the duration, the slower will the query response time be. You need to make wise choice between your query duration requirements and your response time requirements.
  • Sharing vs. not sharing CDRv5 Database. The CDRv5 architecture allows for as many instance of CDRv5 Database as your performance requirement demands. However, there may be a license cost involved with implementing additional MS-SQL instances. If you share the CDRv5 Database, you need to consider every user’s requirements for storage duration.

Database Maintenance (Cleanup)

Database maintenance occurs automatically once daily and optionally when the CDRv5 Client application is launched. You can select this option by selecting ‘Run on application start’ . The database maintenance is implemented as a stored procedure (i.e.; a program inside the MS-SQL Database). This function may use your computer resource and slow it down. It performs many functions such as removing old records and updating many tables that are dependent on the contents of the CDR table. Use ‘Start Now’ to manually launch the database maintenance stored procedure.

Summary Table Update

CDRv5 Application has the logic to summarize incoming CDRs and CPMs and update the summary table on a frequent basis. The default update frequency is 2 minutes. This parameter is configurable.
You can also force an update by clicking ‘Update Now’.

© 2020 Trillys Systems - CDRV5 Web Support