Infor SyteLineFree calculatorPDF, Excel, Word exportInfor SyteLineAll Infor SyteLine (CloudSuite Industrial) tools

SyteLine Upgrade Downtime Window Calculator

This calculator turns the timings from your rehearsal runs into a cutover window for an on-prem SyteLine 8 or 9 to 10 upgrade, or a CSI 10 update weekend. It adds backup, restore, the database upgrade, metadata and FormSync, custom code redeploy and validation, then applies a contingency buffer.

Your numbers

Database size, all databases combined

Backup throughput

MB/s

Restore throughput

MB/s

Upgrade and merge minutes per GB (from rehearsal)

min/GB

Metadata and FormSync

min

Custom assemblies and extended code redeploy

min

Smoke test and validation

hours

Contingency buffer

25 %

Set from the issues and variance you saw in rehearsals.

Your results

Downtime window with buffer

12 hrs

Plan the outage notice and go/no-go points around this figure.

Backup

12.8 min

Restore

17.1 min

Database upgrade and merge

225 min

Window before buffer

10 hrs

Every rate is your own input, ideally from a timed rehearsal on a copy of production. This is a planning model, not an Infor timing figure.

Save results:

Downtime window vs database size

Sweeps Database size, all databases combined from 25 to 1000, holding your other inputs fixed.

Planning your SyteLine 10 cutover?

Send us your rehearsal timings and we will review the window, the sequence and the go or no-go points for your upgrade weekend.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Run at least one full rehearsal on a copy of production and time each step. Enter the combined size of all databases you will move, the measured backup and restore throughput, and the upgrade minutes per GB from the rehearsal (total upgrade tool run time divided by database size). Add the minutes for metadata, FormSync and redeploying custom assemblies and extended code, the hours your key users need for smoke tests, and a buffer that reflects how much the rehearsals varied. The chart shows how the window grows with database size, which is useful when deciding whether to archive or purge history before the upgrade.

Time each step separately in rehearsal, not just end to end
Use production-like storage for the rehearsal, or rates will be optimistic
Rerun the calculator after every rehearsal

Formula

Backup minutes = GB x 1024 / backup MB per second / 60. Restore minutes uses the restore rate the same way. Upgrade minutes = GB x minutes per GB. Window before buffer in hours = (backup + restore + upgrade + metadata + redeploy minutes) / 60 + validation hours. The final window = that figure x (1 + buffer / 100). Backup and restore are linear in size; the upgrade step usually is not perfectly linear because some scripts touch a few large tables, which is another reason to base the per-GB rate on your own data and keep a buffer. Compressed backups change throughput in your favour; measure them rather than estimating.

What happens during a SyteLine 10 upgrade

For SyteLine 10 the upgrade consolidates the separate application, forms, objects and templates databases of earlier versions into one all-in-one database, then upgrades the schema and data. Form customizations made in WinStudio are carried forward by FormSync, which synchronizes form definitions between the old and new metadata. FormSync does not carry IDO, stored procedure or other database-level changes; those must be reapplied or redeployed separately, which is what the redeploy input is for. After that come metadata cache refresh, client and utility server checks, and the user validation that decides go or no-go.

Worked example

With the defaults, 150 GB backs up at 200 MB/s in 12.8 minutes and restores at 150 MB/s in 17.1 minutes. The upgrade at 1.5 minutes per GB takes 225 minutes. Adding 60 minutes of metadata and FormSync and 45 minutes of redeploy gives 359.9 minutes, about 6.0 hours, plus 4 hours of validation for 10.0 hours. A 25 percent buffer makes the window about 12.5 hours. Doubling the database to 300 GB pushes it past 17 hours, which is the point at which a Friday evening start stops fitting comfortably in a weekend with a rollback option.

Frequently Asked Questions

How long does a SyteLine upgrade take?

The project takes months; the cutover weekend is what this tool estimates. For a mid-sized database with moderate customization, windows of roughly half a day to a full day are common, but only your rehearsal timings give a reliable number. Size, storage speed and the amount of custom code drive it.

Does upgrading SyteLine also upgrade SQL Server?

No, they are separate steps. Check the SQL Server versions supported by your target SyteLine release, and if you need a newer SQL Server, upgrade or migrate it in a separate, earlier change so you do not stack two risks on one weekend. Restore to the new SQL Server version during rehearsal.

What does FormSync carry forward?

FormSync synchronizes WinStudio form definitions and customizations between metadata versions. It does not carry IDO changes, stored procedures, triggers or other database customizations; those must be reviewed and redeployed as part of the upgrade plan.

How big should the contingency buffer be?

Base it on rehearsal variance and open issues: if two rehearsals differed by 20 percent and you still have unresolved data fixes, 25 to 50 percent is reasonable. Also set a hard go or no-go time, after which you restore the original databases and reopen the old system.

If you want to use the upgrade to add a private AI layer that answers questions over your SyteLine 10 data on your own servers, we can plan it into the same project.

Talk to an Expert Explore More Free Tools