Migrate Adaptiva SQL Database
This article provides an overview of the steps required to migrate the Adaptiva OneSite database to new hardware while keeping the Adaptiva server on the existing machine, thereby allowing you to reduce the load on the current server, improve performance, and centralize SQL management.
Prerequisites
Verify you have sysadmin permissons on the new SQL server to migrate the Adaptiva database to the new server.
If your Adaptiva Server is integrated with ConfigMgr and the ConfigMgr database will be on a different SQL Server, you must ensure SPNs (Service Principle Name) are created and Kerberos delegations are set up. This will ensure communication between the Adaptiva SQL database and ConfigMgr SQL database.
For additional information please see SPNs and delegation
Download and install SQL Server Management Studio.
1. Stop Adaptiva server services
Perform the following on the origin Adaptiva Server.
Open Windows Services and right-click on AdaptivaServer and select Properties.
Click the Stop button and select Disabled from the Startup type dropdown.
Click OK.
Note: Ensure there are no external systems that will change this setting. Scheduled Tasks, Service Monitoring utilities, etc. Temporarily disable those if they exist.

2. Backup the Adaptiva database
Follow these steps to back up your database via Server Management Studio (SSMS), Create a Backup
3. Transfer database backup to new SQL server
Transfer the file to the new SQL Server (e.g., network share or file copy).
Confirm the file exists on the new SQL Server, is not corrupted, and is accessible locally.
4. Restore Adaptiva database on new SQL server
Perform the following on the destination SQL Server
Follow these steps to back up your database via Server Management Studio (SSMS), Restore a database.
5. Configure SQL server permissions
Update the following T-SQL script with the origin SQL Server
<DomainName>\<ComputerName>and run it from SQL Management Studio:
This will ensure that the permissions are retained after the database restoration.
6. Update Adaptiva database configuration
Open the Registry and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Adaptiva\server\.Find
setup.adaptiva_db_optionand change the value to3.
This will update the Specify Options For Creating The SQL Database settings of the Adaptiva upgrade.
OPTIONAL updates to database configuration
Configure the following settings if appropriate:
If using a named SQL instance on a new SQL server machine, you must change the instance name on the
HKEY_LOCAL_MACHINE\SOFTWARE\Adaptiva\server\setupadaptiva_db_sql_named_instanceline in the registry.If using the default instance, you must leave the
HKEY_LOCAL_MACHINE\SOFTWARE\Adaptiva\server\setup.adaptiva_db_sql_named_instanceline blank in the registry.If not using the default SQL port 1433, you must set the port on the
HKEY_LOCAL_MACHINE\SOFTWARE\Adaptiva\server\setupadaptiva_db_port line in the registry.If moving the database to a remote system not co-located with the Adaptiva Server service, the Adaptiva Server requires the
sysadminpermissions to the new SQL server to change the database name in the registry.
7. Run Adaptiva server setup
Run
adaptiva-server-<version>-windows.exeon the existing Adaptiva Server, and select Advanced Upgrade.
Click Next until you reach the Specify Options For Creating The SQL Database.
Ensure Create The Database In The Same SQL Instance As ConfigMgr Site Database is selected.

Click Next and at the Pre-requisites dialog click Continue.
On the Provide Information for the Database page, click to disable Create the Database in the Site Database Server and Use Same SQL Login Settings.
Under SQL Login, enter a SQL Server Machine Name of the FQDN of the destination SQL Server.
Leave Use Adaptiva Server's Local System Account checked.
Click Next. At the prompt, click Yes to confirm the account.
Click OK. Then click OK to confirm that the SQL Servers are linked.
Complete the install wizard and verify that the post install checks pass.

8. Validate migration
Perform the following on the Adaptiva server.
Ensure that the AdaptivaServer service is started.
Log in to the Adaptiva Admin Portal and ensure dashboards are visible.
Confirm clients are able to communicate with the server.
Monitor SQL activity to ensure the new database is being used.
Last updated
Was this helpful?