Micros 9700 Closed check detail history

[mbhutchins]

I am having problems running the closed check reports at end of day and in report writer. Over night reports can take hours and report writer times out trying to run them.
It's not a daily problem mainly after a series of busy weekends. Daily reports normally take less than 30 minutes.

I looked at the Check tables it is going back 44 days, almost 7 weeks. It and would includes 7 Saturdays when ran on a Monday our busiest day. The microsdb.check_detail table had more than 2.5 million records.

I saw that 3700 keeps 14 days, how many days does should and can it be set somewhere.

The only setting I could find in EMC Number of months to keep totals and it is set to 13 months.

We also have a Web Reports server on a different machine that has check history so we don't need as much on the Micros Server available to Report Writer. Plus the .txt reports are kept on the server and backed up.

Thanks

 

[mbhutchins]

I got this from Oracle from 9700_Totals_Purging_White_Paper.pdf

They said the limits are hard coded in mrdb. I guess I could run a delete query on CHECKS and Check CHECK_DETAIL but not real comfortable doing that. Not sure of any other relationships that might be impacted.

How long is other data in the 9700 saved?
In order to keep the database size from growing out of limit, 9700 has already been purging the following types of data. The values shown below are the pre-defined retention periods; when data in these tables is older than the retention period, the data is purged from the database using a similar mechanism that is used for totals purging.
• Checks data – 6 weeks
• Time card details – 2 months
• Audit Trail data – 1 month
• Client Event data – 1 month
• Authorization log data – 1 month
• Pos Journal log data – 3 months
• Transaction log data – 3 months
• Activity log data – 1 month
• Signature data – 1 week
• Dead strings
Dead strings refer to strings that are no longer being used by the database. Each time when MRDB purging thread wakes up, it will scan all the strings to determine which ones are no longer being used and will purge them correspondingly.