Questions and answers about the Purge Process in Mail360 Data Manager

Q:  How do we know if the purge is actually running, and not in some sort of loop?

Support : There are system level stored procedure available in SQL through which the  DBA can know whether purge stored procedure is running or not.

Q:  When getting the partition dates, can we use the newest date for the purge, or do we need to run all partition dates, sequentially?

Answer:  It depends upon the amount of data present at each partition.  If the amount of data is huge in every partition, then purging with newest date will take a long time.

Q:  Our maintenance window is limited to 4 hours with the possibility to extend to 6 hours. How can we execute the process to ensure we can complete the purge of data within the designated maintenance window?

Answer:   Running the purge procedure for a couple of Partitions will give an approximate time taken to complete a purge process.  Based on that calculation , you can figure out whether the whole purge process will complete within the maintenance window.  If not you can perform the same process in the next available window.

Q:  Right now we are using the run date option. What if we want to use the retention days option, how different will that be, and how it will affect the DB?

Answer:   As per the Purge procedure , by default the Retention Default is set to 120 days.
If the Rundate is not provided , then Stored procedure will take the current date. And it will purge all the data older than 120 days from the current date.

**Note:  The MAIL360_Data Manager_Operations_Guide_xxx.pdf) can be referenced for information about the Purge process.
UPDATED:  April 20, 2017