1. Accumulative database (check.udb) optimization

1.1. General information

1.1.1. Several ways to optimise accumulative database

1.1.1.1. Delete obsolete common shifts

1.1.1.1.1. On manager station open service -> common shifts information :

1.1.1.1.2. Select the shifts you wish to delete from accumulative DB :

1.1.1.1.3. To filter data by restaurant, date or cash server it's more convenient to change view mode to table :

1.1.1.1.4. Then press "wipe database" (select no objects when pressing):

1.1.1.2. Start new DB periodically

1.1.1.2.1. You are able to move check.udb somewhere from time to time in order new accumulative DB to be created.

1.1.1.2.2. You may also delete this file and restart report server (completely clean up accumulative database).

1.1.1.2.3. You must do "export of check.udb" to external DB in order to clean that up (if empty new DB export goes - it will erase data from corresponding tables in external DB).

1.1.1.2.4. In order to delete agreates ("IR_" tables), use custom scripts.

1.1.1.2.5. If you use ultra light mode of internal accumulative DB ("check.udb" by default), you can delete and recreate external (MSSQLS) DB in order to clean up data about front office work history.

1.1.1.3. UDB database mode

1.1.1.3.1. You are able to change check.udb mode to light in order to save all data to external DB to avoid huge UDBs processing failures.

1.1.1.3.2. Use manual 2.2.3. for additional choice investigation.

1.1.1.3.3. You must change to light mode in case of near size limit (2GB) accumulative DB (check.udb) state obligatory. No any new shift data can be pumped in oversized DB with 'File write error'.

1.1.1.3.4. In order to reduce internal DB you have to:

1.1.1.3.4.1. Set proper external DB connection (if not yet exists) and manually export accumulative data to that before mode parameter change.

1.1.1.3.4.2. Change 'UDB database mode' parameter value to 'Light' and internal DB will be reduced automatically.

1.1.1.3.4.3. Manually copy shift files from \archive\ to \incoming\ for reloading into external DB accumulative tables if necessary.

1.1.1.3.5. You have to do this for each report server that is set to gather accumulative data.

2. Cleanup temporary files

2.1. Make a periodical removal of temporary files.

2.2. Make periodical manual backup cleanup and perform smart backup management.