Res 3700: Trouble /w table trans_archive_dtl

[PopTin]

Hi there,

we having issue with table trans_archieve_dtl. Because my transaction analyzer shows no data since '2014-12-26', I checked table trans_archieve_dtl. The result shows that table trans_archieve_dtl holds historical data only until '2014-12-26'. After that day, it just stopped update historical data without knowing why?

Any suggestion on that?

 

[BootstrapperRI]

That table is populated from a few other data tables in the DB. The number of days it will hold data is determined in the POS Config. Check under Reporting > Historical Totals and select the tracking total currently in use.

Warning: transaction detail is extensive and will increase the size of the DB file on the system. Increase the number of days at your own risk. Standard on new systems (plenty of disk space and processing power) is 120 days, although I have seen sites at 400 days.

Run TA in an auto sequence and archive the output if needed.

These changes will not populate the data prior to 2014-12-26, just moving forward.

 

[pmegan]

Check the setup in your historical totals classes to see what kind of retention time you have for trans archive. My company has 20 very busy restaurants with the retention set to 90 days, and our databases are generally between 700M and 1.1G.

Historical totals determine how long to keep data before purging it, but that's now the problem you're having. This sounds like you just don't have an autosequence set to post though. You should have one running frequently, like every 10 minutes or more often if you're busy, that contains a step with the "post trans archive detail" stored procedure.