Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

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

Migrate a new SQL DBO account to a new SQL instance

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 1,111 Votes: 0 Revisions: 11


Migration of a new 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 SolarWinds_NPM2 and create a new password.
  6. Click Finish once the process completes.

You can also delete the SolarWinds_NPM account in the SWL 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 (SolarWinds_NPM2) 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