Overview
When payroll transactions are not consolidated, PayGlobal creates additional transaction lines. This increases database storage usage over time.
The actual impact depends on how many allowances are changed and how many additional transaction lines those changes create.
How to consolidate or unconsolidate payroll transactions
The Payroll consolidate transactions setting is configured for each allowance.
-
Open Organisation | Entitlements | Allowances.
-
Open the relevant allowance and select the T&A Rostering (ii) tab.
-
Set Payroll consolidate transactions to one of the following options:
-
Yes: transactions accumulate and are shown as one transaction in Payroll.
-
No: transactions are shown separately, such as daily transactions.
-
-
Repeat the setting for each allowance that requires the same treatment.
If you export transactions from Time and Attendance or Rostering to Payroll, make sure the Consolidate transactions setting on the T&A/Rostering allowance matches Payroll consolidate transactions on the associated Payroll allowance. When effective rates are used, setting both fields to No helps retain the day on which each transaction was worked.
Changing the setting affects transactions created after the change. It does not consolidate or unconsolidate existing transactions.
Estimated storage impact
For estimation purposes, if each additional transaction creates one extra line in each of the InputAllowance, CurrentAllowance, and HistoricalAllowance tables, the combined storage requirement is approximately 3,000 bytes per transaction.
Based on this estimate:
-
Approximately 333,333 additional transaction lines would use around 1 GB of storage.
-
A 20 GB storage block would support more than 6.5 million additional transaction lines before another storage block was required.
These figures are estimates only. Actual storage usage may vary depending on the transaction data and database configuration.
Expected impact
For most customers, changing to unconsolidated payroll transactions is unlikely to have a significant impact on storage in the short term.
Over the longer term, the additional transaction lines will contribute to database growth. We recommend including the regular purging of older closed pays in your normal PayGlobal database maintenance.
Closed-pay information and purging
PayGlobal retains closed-pay information in historical tables. Purging removes the corresponding data from the current transaction tables, while historical allowance data remains available for viewing and reporting.
Recommendations
-
Estimate the number of additional transaction lines expected from your payroll configuration.
-
Monitor database storage usage after changing to unconsolidated transactions.
-
Regularly purge older closed pays as part of your normal database maintenance process.
For more information, see PayGlobal Maintenance.