Submit a ticketCall us

AnnouncementsTHWACKcamp 2018 is here

2018 is the seventh year for THWACKcamp™, and once again we’ll be live October 17 – 18 with packed session tracks covering everything from network monitoring and management, to change control, application management, storage, cloud and DevOps, security, automation, virtualization, mapping, logging, and more.

Register for online sessions.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Migrate a SQL DBO account to a new SQL instance

Migrate a SQL DBO account to a new SQL instance

Table of contents
Created by Interspire Import, last modified by Jeremy Holmes on Jul 19, 2018

Views: 1,146 Votes: 0 Revisions: 14


Migration of a SQL DBO account to a new SQL instance fails.


This issue occurs when an old account is still associated to an old SQL instance and not the new SQL instance.


Note: Before doing any work on your database, please make sure that you have a current backup as this will make permanent changes to your database.

  1. Transfer the backup file (.BAK) to a new SQL server and restore.
  2. Run the Configuration Wizard - Running the Configuration Wizard.
  3. Use SA or Windows Authentication to connect to the SQL instance.
  4. Select Database and choose New Account on the third window that will appear.

  5. Name the account SolarwindsOrionDatabaseuser2 (or something besides the old account) and create a new password.
  6. Click Finish once the process completes.

You can also delete the SolarwindsOrionDatabaseUser account in the SQL Server Management Studio after the database migration so that only one DBO account exists. For SQL DBO accounts that were migrated successfully, you can create a new account (SolarwindsOrionDatabaseUser2) for them. This also ensures that Orion NPM has the required access to the migrated database.

For more information on how to migrate Orion NPM and migrating to a separate SQL server, please refer to the following documents:

Last modified