Purging the Submissions History table
Updated: 2009-04-30
In the application database, there is a table named Submissions. This table is used for auditing purposes. Keep this table data for future auditing.
This table contains the change list for every submission a Planning Server system user submits. The change list can be extensive, so the size of this table can grow very large and occupy a lot of space. For example, an average update submission of 78,000 cells will insert a record into this table, and that record will add approximately 6 MB to this table. Your database administrator needs to monitor the space growth of this table and periodically back it up and then purge it to keep the database from growing too fast.
Warning
The database administrator must back up this table before purging it. This table contains data that is used for auditing and may have legal consequences.
Example
Call the following stored procedure, which is installed on the application database when you create the application database to perform the table purge. It takes one parameter of @PurgeDatetime. It will delete all data that is older than the parameter that you specify for @PurgeDatetime.
The following example shows how to delete all submission history that has a CreateDatetime value that is earlier than 2007.
DECLARE @RET int
EXEC @RET = bsp_SubmissionsPurge @PurgeDatetime = ‘12/31/2006’
SELECT @RET
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Planning Server.