# SyteLine SQL Server Version Upgrade Checklist > Source: https://netray.co/tools/syteline-sql-server-version-upgrade-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step by step checks for upgrading the SQL Server under SyteLine 9 or 10, in place or side by side, including reconnecting the application tier. ## Category syteline ## Erp Infor SyteLine ## Audience - DBA - ERP administrator - Infrastructure engineer ## Tool **Kind:** checklist **Groups:** #### Compatibility **Items:** **Text:** Confirm the target SQL Server version is on your SyteLine release's supported list in Infor's system requirements **Critical:** true **Text:** Decide the database compatibility level policy (keep the old level first, raise after testing) **Critical:** true **Text:** Confirm the new instance collation matches the original exactly **Critical:** true Compare sp_configure settings between old and new instance (clr enabled, max degree of parallelism, cost threshold for parallelism) List linked servers on the old instance and what uses each one Choose in-place or side-by-side; side-by-side keeps the old server as a rollback #### Before the move **Items:** **Text:** Full backups of every SyteLine database, including any separate forms, objects or templates databases on older releases **Critical:** true **Text:** Script logins with their SIDs and passwords (for example with sp_help_revlogin) so database users map without orphans **Critical:** true **Text:** Script SQL Server Agent jobs: index and statistics maintenance, backups, and any custom jobs that touch SyteLine databases **Critical:** true Script linked server definitions and their security mappings **Text:** Back up the SSRS report server databases and the report server encryption key **Critical:** true Record the old server name, instance name and port used by every application tier connection #### The move **Items:** Restore the databases on the new instance (side-by-side) or run the in-place upgrade **Text:** Create logins, then find and fix orphaned users (ALTER USER ... WITH LOGIN) **Critical:** true **Text:** Re-create SQL Server Agent jobs and confirm SQL Server Agent is running **Critical:** true Re-create linked servers and test each one Set max server memory explicitly Configure tempdb with multiple equally sized data files Restore the SSRS encryption key on the new report server if it moved #### Reconnect the application tier **Items:** **Text:** Update Configuration Manager configurations to the new server and database names **Critical:** true **Text:** Update Service Configuration Manager entries for TaskMan, replication and event services **Critical:** true Restart the IDO Runtime Service and other SyteLine services Check the ION connection still reaches the application database and outbox Update report server data sources to the new server #### Validate **Items:** **Text:** Log in and open key forms at every site **Critical:** true **Text:** Run a report through TaskMan and confirm it appears in Background Task History **Critical:** true Post a test transaction in a test site or controlled entry and reverse it Check replication between sites and the Replication Document Outbox and inbox Confirm BODs flow to and from ION Review LogMonitor and the SQL Server error log for errors #### After go-live **Items:** Update statistics on all SyteLine databases with a full scan where time allows Run index maintenance on the new instance Monitor wait statistics and slow queries for a week, comparing with the old server Raise the compatibility level only after testing, and watch for plan regressions Decommission the old instance only after a full month-end close **Scoring Note:** 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. ## Content **Intro:** 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. **Sections:** #### In place or side by side **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How do I upgrade SQL Server for an ERP database? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sql server version upgrade, how to upgrade sql server, upgrade ms sql server, microsoft sql server upgrade, upgrade sql server database, syteline sql server upgrade, side by side sql server migration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json