Most data in Servicing Director remains in Servicing Director for auditing, historical, and licensing reasons.

Therefore, expect the data stored to continually grow. Since there are few options for removing, purging, or deleting old data from Servicing Director, consider utilizing the options below to save space.

• Servicing Director by default does not have a growing Microsoft SQL Server database log file, because as installed the databases has the Microsoft SQL Server setting of "Simple recovery mode". However, if your administrator has chosen to enable a "full recovery mode", then be sure to use Microsoft procedures to manage the space the enabled log file takes up.
• There are a handful of Event Manager application events that can remove a few temporary records from the database. They are usually already enabled as part of your implementation of the product. You can still check that they are run periodically. You can find them in the Event Manager available events under System Administration > CleanUp Functions. Some of these would apply to your business and some possibly not, but most likely you have the ones that apply already scheduled to run once a month or so. When these run, the space freed is minimal, and their main purpose is to prepare for more transactions of the same type, rather than to save space.
• If you have the Servicing Director Archiver feature enabled, search Knowledge Center with the key words Servicing Director Archive Folder for more information about managing the size of the Archiver.

ArticleNumber:

000047407