This site uses advanced css techniques
Most of the housekeeping tasks in the iSystems Evolution™ payroll service-bureau system are done by administrators using the EEC (Evolution Enterprise Controller), but one common task — rebuilding the temporary tables — can be done from the Evolution application client itself. This Evo Tip provides instructions for how to perform this.
Rebuilding TMP_TBLS requires admin rights, so it may be required to login as the explicit admin user - this will become apparent if the required menu items are not found on user's menu as shown.
Click SB Admin, then Maintenance
Set the number of threads, which is normally based on the number of processors on the target DB servers. If you're rebuilding just a few files, then this setting doesn't matter, but if you have absolutely no idea what to choose, pick 4.
Then click Rebuild Temporary Tables, and confirm when asked.
Note that this does not actually launch the rebuild process yet, there's still one more entry required.
|Just one client|
|Multiple individual clients|
|Range of clients|
Rebuilding of temp tables is done one client at a time per thread, and for small numbers of clients (one or two) it will complete very quickly. This process may be run during live production, though for doing full rebuilds it's recommended to wait until the off hours due to the amount of time it takes and the load it puts on the system.
Progress is shown in the Current status display, and the last numbers (m/n) shows how many (m) of the total (n) have been completed.
Note - there is no elegant way to interrupt a temp-table rebuild.
After doing a full rebuild of temp tables, it's recommended to sweep (backup and restore) the TMP_TBLS.gdb file on the Linux database server to essentially defragment the file and improve performance. This sweep process can only be done while Evolution is offline.
This is not necessary or recommended when rebuilding just a few clients.
2007/06/26: First published