CCE database full

[rsboom]

We have a customer with CCE 4.1.1

The database ASMSData1 is full, how can we correctly delete/archive parts of the database so the customer has recent information. (it is limited to 4GB, due to sql express).

It there a simpel script to do this?

Many thanks in advance!

[pradeept]

reply to cce database full

CCE 4.0 introduced a new database structure.

It’s design objectives were:
• Keep all relevant data for an interaction in the same physical location
• Archival of data should be automated if possible, with a manual override
• Archival of data should co-exist peacefully with a 24/7 operation of contact centre
• Reporting should interfere as little as possible with online CCE operation
• Reporting should work identically across current and archival data, combining databases as required
• Have third party reporting packages able to transparently use our mechanism

To achieve the above, the CCE 3.x ActiveInteractionData and ASMediaStore databases were combined into a new database subsystem fronted by the ASMSControl database. This in turn spawns and manages a series of ASMSDataX databases (where X=1,2,3 … ,n).

ASMSControl contains all the database code in the form of stored procedures, triggers and functions. It also contains some data:

• <LI style="mso-list: l0 level1 lfo2" class=MsoNormal>cached summaries of presently active interactions
• small amounts of relatively static reference data

It writes all detailed interaction based data into the current ASMSDataX database where it is stored permanently. Each of these databases contains data only – all code remains in ASMSControl, and all programs (mediastores and reporting) using the databases reference only ASMSControl. New empty ASMSDataX databases (each covering a future period) may be set up in advance. Detailed data for interactions occurring within the prescribed period will automatically end up in the corresponding ASMSData database.

This mechanism provides CCE with an on-the-fly ‘archival’ system that writes data once only. Reporting and other data retrieval functions address ASMSControl which decides which group of ASMSDataX databases to examine. Data retrieval then occurs across these databases, minimising impact on ASMSControl and the current ASMSData databases.

All mediastores and other database addressing servers now write to ASMSControl, not to other databases. ASMediaStore is no longer used. ActiveInteractionData remains only if detailed call event information is wanted from the IDS Server. If not, then it too disappears.

Throughout the ASMSControl and ASMSDataX databases all date and time fields are in UTC format, unless specifically noted as otherwise.

Future database code changes will affect only ASMSControl and will be applied by a system similar to our present database upgrade system. Less frequent data structure changes may apply to ASMSDataX databases. These will be automatically applied by ASMSControl - it knows the names and whereabouts of all the ASMSDataX databases. In this way all ‘archival’ databases will be kept current and reporting software will continue to be able to accurately scan historic data.

So putting it in a simple words, starting from CCE 4.0 onwards there is no option of purging or scripts that can be provided for data purging. Customer need to create new ASMSData database and have all the interaction stored in that database.

[rsboom]

Thank you for your detailed reply! Will look into it and reply a little later...

[andreas1]

Or you can just upgrade to SQL full version (since SQL Express is supposed to be for lab environment) and don't worry about space limitations