SyteLine SQL Server Version Upgrade Checklist
This checklist covers upgrading the SQL Server instance under an on-prem SyteLine 9 or 10 system, in place or by moving to a new server side by side. It covers the SQL Server work and the SyteLine application tier steps that DBAs often miss.
0 of 35 items complete
13 critical items still open - these are the highest-risk gaps.
Compatibility
Before the move
The move
Reconnect the application tier
Validate
After go-live
Count the critical items still open. Do not start the cutover with open critical items in Compatibility or Before the move; those are the ones that cannot be fixed afterwards without a rollback.
Get your SQL Server move plan reviewed
Send your current and target SQL Server versions, database list and multi-site layout and we will review the plan and the reconnect steps.
Optional. The tool and every export work without this. No spam.
In place or side by side
An in-place upgrade runs SQL Server setup over the existing instance. It keeps names and logins but leaves no easy rollback once it starts. A side-by-side move installs the new version on a new server or instance and restores the databases there. It needs more preparation, logins, jobs, linked servers and report server keys, but the old server stays untouched as a rollback until you decide to retire it. For an ERP that the plant runs on, side by side is the usual choice. Either way, confirm first that your SyteLine release supports the target SQL Server version: check Infor's system requirements for your exact release and do not rely on general SQL Server compatibility.
SQL Server details that break SyteLine
Collation must match the original exactly; a different server collation causes errors when SyteLine code joins temp tables to application tables. Logins must be moved with their SIDs so database users map without becoming orphans; sp_help_revlogin from Microsoft is the usual tool. SQL Server Agent must be running for the backup and maintenance jobs you moved. Restore databases at their old compatibility level first and raise it only after testing, since the newer cardinality estimator can change plans for heavy SyteLine queries. Multi-site setups spread across servers often rely on linked servers, which must be re-created with the same names and security.
- Collation identical to the original
- Logins moved with SIDs, orphaned users fixed
- SQL Server Agent running
- Compatibility level raised only after testing
Reconnecting SyteLine to the new server
SyteLine does not find the new server on its own. Configuration Manager holds the configurations that map users to databases; update each to the new server and database names. Service Configuration Manager holds the TaskMan, replication and event service settings; update those too, then restart the IDO Runtime Service and the other services. Point report server data sources at the new server. If SSRS moved, restore its encryption key on the new report server or stored credentials and subscriptions will not work. Check that ION still reaches the outbox. Then use LogMonitor while users open forms to catch any connection still pointing at the old name.
How to validate before handing back
Run a short script of checks at every site: log in, open key forms, run one report through TaskMan and see it in Background Task History, post and reverse a controlled transaction, and check replication and BOD flow. Read the SQL Server error log and LogMonitor. In the first week, compare wait statistics and slow queries with a baseline taken on the old server; plan regressions usually show up in large reports and MRP. Update statistics and run index maintenance soon after the move. Keep the old server until a full month-end close has run on the new one.
Frequently Asked Questions
How do I upgrade SQL Server for an ERP database?
Confirm the ERP release supports the target version, back up everything, then either upgrade in place or install the new version side by side and restore the databases. Move logins with SIDs, jobs and linked servers, keep the old compatibility level at first, reconnect the application tier and validate with real transactions before go-live.
Which SQL Server versions does SyteLine support?
It depends on your exact SyteLine or CSI release and changes as Infor certifies new versions. Check the system requirements document for your release on Infor's documentation or support portal. Do not upgrade SQL Server beyond what your release lists, even if the database restores without errors.
What is the safest way to upgrade Microsoft SQL Server?
Side by side: install the new version on a new server or instance, restore the databases, move logins, jobs and keys, and test before switching users over. The old server stays as a rollback. In-place upgrades are faster but leave no simple way back once setup starts.
Should I change the compatibility level after upgrading SQL Server?
Not immediately. Keep the old compatibility level after the move, confirm everything works, then raise it in a test environment and compare plans for heavy queries. A newer level can change the cardinality estimator and query plans, which can slow some large reports even as others improve.
If you want your team to ask SyteLine questions in plain English on the new server, we can add a private AI layer on your own infrastructure with read-only access.
Related Tools
SyteLine 8/9 to 10 Technical Upgrade Checklist
The technical steps for moving an on-prem SyteLine 8.x or 9.x system to SyteLine / CSI 10, from customisation inventory to rehearsal and rollback.
Developer ToolsSQL Server ERP Backup Script Generator
Fill in the database name, backup folder and retention to get a T-SQL script with checksum, compression, verification and backup history cleanup.
ERP OperationsSQL Server Index Maintenance Checklist for ERP Databases
A practical checklist for index rebuilds, reorganizes, statistics updates and verification on SQL Server hosted ERPs.
Developer ToolsSQL Server Wait Types Reference for ERP Databases
Searchable lookup of common SQL Server wait types with plain-language meaning, typical cause in an ERP workload and the first thing to check.
Infor SyteLineSyteLine Utility and Web Server Sizing Calculator
Turn named users, concurrency and your own per-session assumptions into a server count and RAM plan for the SyteLine 10 application tier.
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 Cutover Plan Worksheet
- SyteLine Change Request Form Template
- SyteLine Cycle Count Variance Worksheet
- SyteLine Database Growth Forecast Calculator
Keep exploring
Free tools
- SyteLine to CloudSuite Upgrade Cost EstimatorEstimate what it will cost to move from your current SyteLine version to CloudSuite Industrial, including customization remediation and integration rework.
- SyteLine SSRS Report Server Setup ChecklistServer, SyteLine-side, deployment, test and operations checks for SSRS based report output on SyteLine 9 and CSI 10 on-prem.
- SyteLine Upgrade Regression Test ChecklistA practical regression checklist for SyteLine upgrades across business processes, customizations, reports and integrations.
ERP fixes and how-tos
- Fishbowl Inventory Release Notes, Updates and Upgrade ChecklistWhere to find Fishbowl Inventory release notes, how version updates work for the server and clients, and a safe upgrade checklist for admins before updating.
- Private AI Layer for SyteLine On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to SyteLine on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- How to Build SQL Views for Custom SyteLine ReportingWhy custom SyteLine reports should read from purpose-built SQL views, not core tables directly, and how to build and place those views safely.
Guides
- CloudSuite Industrial 10 to 11 Migration GuideStep-by-step migration guide for upgrading Infor CloudSuite Industrial (CSI) from version 10 to 11, including ION integration, form updates, and testing.
- SyteLine 8 to SyteLine 10 Upgrade GuideSyteLine 10 upgrade guide for SyteLine 8 sites: architecture changes, customization remediation, data migration and testing cycles before go-live.
- SyteLine 9 to 10 Upgrade ChecklistComplete upgrade checklist for migrating from Infor SyteLine 9 to SyteLine 10, covering Mongoose migration, database conversion, and form compatibility steps.
Integrations
- How to build an MCP server for Infor SyteLineHow to build a Model Context Protocol server for Infor SyteLine: which read-only tools to expose, IDO and SQL access, auth, transports, and audit for any MCP client.
- How to connect Power BI to Infor SyteLineHow to connect Power BI to Infor SyteLine: direct SQL Server, IDO or ION API, data warehouse options, on-prem gateway, key dashboards, and natural-language Q&A.