How to Shrink the Size of Various DocAve Databases
Search and filter
KB Article ID: 10225
| Product: | DocAve 6 Suite |
| Product Version: | 5.7.0.0,6.0.0.0 |
| SharePoint Version: | 2007,2010 |
Details:
| DB Name | Used by | Functionality | Growth Rate | Recovery model | Does DocAve have a feature to automatically prune the records in DB (Like job/data pruning)? | Comments |
| DocAve Cache DB | Replicator | Stores Job history, Item Modification history, Dirty Data info, Design Information, etc. | It depends upon how many items need to be replicated. If you replicate 1,000,000 items from the source farm to the destination, then the source Cache DB size is about 1 GB, and the destination Cache DB size is around 1.2 GB. | Simple |
By default, Replicator has a schedule feature that runs the pruning job every 7 days. This cycle time is configurable in a Replicator configuration file (data\SP2010\Replicator\SP2010Replicator.xml). The pruning job deletes the orphan mappings, plans, MH records, etc. in the Cache DB. |
If the DocAve Cache DB is broken, then the next incremental replication job is performed as a full replication job, and the failed-try function will not work. |
| DocAve Stub DB | Extender and Connector | Stores stub information (path, Device ID, etc.) | It depends upon how many stubs are stored in the database. According to our test results, 1,000,000 stubs will consume 300 MB of disk space. | Simple | This database cannot be pruned, but users can utilize the Orphan BLOB Retention feature to delete the orphan stubs in the database in order to reduce database size. | Administrators should treat a DocAve Stub Database similar to a SharePoint content database and back up it regularly. If the Stub Database is corrupted or cannot be connected, an end-user would not be able to access any stub on the SharePoint site. |
| DocAve Control DB | Control Service | Stores plans, job and settings information, etc. | According to our test, if the Control Database contains 80 plans and 15,000 jobs, the database size would be around 2 GB. | Simple | If the job pruning feature is enabled, DocAve will delete the expired job reports from the Control Database. | If the DocAve Control Database is corrupt, then the DocAve GUI will not be accessed. |
| DocAve Auditor DB | Report Service | Stores Auditor items | 10,000 Auditor items consume 5 MB to 10 MB of disk space. | Simple | If Auditor pruning job is enabled, DocAve will delete or export Auditor records regularly. | |
| DocAve Report DB | Report Service | 1. Stores history information for generating trend line. 2. Stores temporary data for exporting a report. 3. Stores DocAve auditor data. |
1. Depends on how may profiles DocAve contains and how often the collector job runs. 2. Depends on how many reports are generated. 3. Depends on DocAve access frequency. |
Simple | 1. No pruning feature. 2. After the exporting report job finishes, DocAve will delete the cache info in the database automatically. 3. No pruning feature. |