- 4 minutes to read

Planning

Depending on the type of move operation, there may be many steps to perform and potentially many competencies required. So make sure to have a plan!

Inform

Ensure all stakeholders are aware of the pending move operation since Nodinite is unavailable for the business/IT-ops/AM-Team during downtime.

Important

Make sure to plan this operation carefully. Verify that all prerequisites are satisfied on new SQL Instances before moving any of the Nodinite databases.

Pre-flight Checklist

Before disrupting any services what so ever you must first make sure the new environment has the proper configurations regarding:

Control Step Description
#1. Version Same or a newer version of SQL Server? Can you detach and attach the database files, or do you need to perform a backup and restore operation? The latter takes more time. In addition, the SqlPackage.exe may need to be updated; Make sure to match the folders accordingly.
#2. SQL Server instance name New name on new SQL Server instance? (named or default instance) Cluster and Listener names are virtual names and can be re-used in the new environment
#3. Firewall What firewall policies exist in the old environment? Make sure to open the necessary ports for the new environment
#4. Linked Server(s) Make sure the new environment has the corresponding Linked Servers setup as in the old environment. If you are using AOAG, ensure they exist on all nodes. Without these, Nodinite can't access the other databases and the creation of new Log Databases will likely fail
#5. MSDTC Nodinite relies on this service Make sure the new environment has the same configuration as the old one meeting the Nodinite prerequisites
#6. SPNs registered Kerberos requirement in a distributed environment This step depends on the type of the new SQL environment and if you are using Logging from BizTalk Server and/or uses SQL Server Always-On
#7. Trusted for delegation To get Kerberos operational in a distributed environment Applies to distributed environments
#8. Access rights Nodinite New accounts must have same set of rights. Ensure they exist as Users in the Administrators Role. Copy from the old environment

Prepare the New SQL Server Instance(s)

Regardless of the type of new SQL Server instance to use, you must conform to the prerequisites.

The new SQL environment may be either of:

  • Stand-alone
  • Fail-over cluster
  • SQL Server Always On (AOAG)

Linked Servers

You must properly configure the set of Linked Servers. Review the linked guide before proceeding.

According to the table below; You need to add the same set of Linked Servers for all that apply. If the new SQL environment is the same type as the old one; Copy/script the old Linked Servers using SSMS.

Product SQL Environment Step Comment
Nodinite Default instance Make sure there is a Linked Server for 'localhost\instancename' Repeat for other external SQL Server instances with Nodinite databases
Nodinite Named instance Make sure there is a linked server for 'localhost\instancename' Repeat for other external SQL Server instances with Nodinite databases
BizTalk (BizTalkMgmtDB) Default instance Make sure there is a linked server for 'BizTalkSQL[ClusterMGMTInstance]Name'
BizTalk (BizTalkMgmtDB) Named instance Make sure there is a linked server for 'BizTalkSQL[ClusterMGMTInstance]Name\instancename'
BizTalk (BizTalkDTADb) Default instance Make sure there is a linked server for 'BizTalkSQL[ClusterMGMTInstance]Name' If this database is in another instance than the BizTalkMgmtDb
BizTalk (BizTalkDTADb) Named instance Make sure there is a linked server for 'BizTalkSQL[ClusterMGMTInstance]Name\instancename' If this database is in another instance than the BizTalkMgmtDb

All Linked Server configurations must have the Security option 'Be made using the login's current security context' and the two Server options RPC enabled

MSDTC

Review the MSDTC user guide.

Prepare the Nodinite Application Servers

If the new SQL Server instance is running with a higher version, you must update the SQLPackage (DACPAC) on the Nodinite Application Server to match the new version. In addition, you must change the SqlPackageExecutable system parameter with information about the new path, which includes the new version number.

Before continuing with the following steps, make sure to perform the steps with consideration to the prerequisites.

Next Step

Ready to execute your migration? Choose your migration type: