SyteLine Database Growth Forecast Calculator
Database growth is easy to ignore until backups overrun their window or a disk fills. Enter your current size and monthly growth to see projected size, the effect of archiving and the storage you need for backups and test copies.
Your numbers
Data and index size from SQL Server, excluding the log file.
Take it from the size at month ends over the last 6 to 12 months.
Estimate from old transaction and log tables you can safely archive.
Production plus test, development, training and so on.
Your results
A planning estimate using linear growth. Add allowance for the transaction log, tempdb, differential and log backups, and headroom. Check archive options against your SyteLine version and retention rules before deleting data.
Database size over time (GB)
Sweeps Planning horizon from 1 to 60, holding your other inputs fixed.
Get a table level growth analysis
Optional read-only review of what drives growth in your SyteLine database.
Optional. The tool and every export work without this. No spam.
How to use the calculator
Take your current database size from SQL Server management tools, and compute monthly growth from several month end readings rather than a single month. Set the horizon you are budgeting for, an honest archive estimate, the number of full backups you keep and how many environment copies exist. The chart plots projected size with and without archiving across the horizon.
- Measure growth over at least six months.
- Include every environment copy.
- Treat the result as a minimum.
- Re-measure each quarter.
The method
Projected size equals current size plus monthly growth times months. Archiving reduces that by a percentage. Backup storage equals projected size times the compression ratio times the number of retained full backups, and environment storage equals projected size times the number of copies. The model is deliberately simple. If volume is rising, use a higher monthly figure or run the calculator for two scenarios.
Where SyteLine data grows
Growth typically comes from transaction history such as inventory and material transactions, job transaction data, ledger postings, audit and activity logs, and attached documents or images if stored in the database. Identify the biggest tables with a standard SQL Server size report before deciding what to archive, and agree retention periods with finance, quality and audit first.
Common mistakes
Planning only for production, forgetting that restores need free space, keeping backups on the same disk as data, and deleting history without checking regulatory retention such as aerospace traceability records. Also rebuild or reorganize indexes on schedule, since fragmentation wastes space and slows queries.
Frequently Asked Questions
How do I find my current database size?
Use the SQL Server database properties or a standard disk usage report for the database, and note data and log sizes separately. Record the figure at each month end so trends are visible.
Is linear growth realistic?
For a stable plant it is a fair first estimate. Growth often steps up after new sites, more shop floor data collection or EDI volume. Add a scenario with a higher monthly rate to see the effect.
Can I archive any data safely?
Only data past the retention period set by finance, quality and legal, using a supported archive or purge approach for your version. Always test on a copy first and keep a verified backup.
What compression ratio should I assume?
SQL Server backup compression commonly reduces size to roughly a third to a half for ERP data, but results vary. Measure a recent compressed backup against database size and use that ratio.
If you want a read-only analysis of which SyteLine tables drive your growth and what is safe to archive, we can run one against your database copy.
Related Tools
SyteLine Cycle Count Variance Worksheet
An editable cycle count sheet that computes variance quantity, variance value and record accuracy per line and overall.
Infor SyteLineSyteLine Change Request Form Template
A change control form for SyteLine configuration, customization, patch and integration changes with impact analysis and rollback plan.
Infor SyteLineSyteLine Cutover Plan Worksheet
An editable cutover runbook with sequence, owner, planned duration, rollback point and a running total of the cutover window.
Infor SyteLineSyteLine Downtime Cost Calculator
Quantify the hourly, monthly, and annual cost of SyteLine outages using your revenue, labor, and operational dependency profile.
More Infor SyteLine tools
See all- SyteLine Form Personalization Checklist
- SyteLine User Access Request Form Template
- SyteLine Custom Report Request Template
- SyteLine Data Conversion Mapping Worksheet
- SyteLine UAT Test Script Worksheet
- SyteLine Reorder Point and Safety Stock Calculator
- SyteLine EOQ and Lot Size Calculator
- SyteLine Job Cost Estimate Calculator
- SyteLine Scrap, Yield and Start Quantity Calculator