Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > Use remote Microsoft SQL Server as database

Use remote Microsoft SQL Server as database

Table of contents
Created by Aileen de Lara_ret, last modified by MindTouch on Jun 23, 2016

Views: 18 Votes: 0 Revisions: 2

Overview

This article provides steps to use a remote Microsoft SQL server as a database. 

You can improve the performance of your Orion Network Performance Monitor by offloading the SQL transaction processing from your Orion server to a remote Microsoft SQL Server.

Environment

All NPM versions

Steps

1. Close all Orion applications currently running on your Orion server.
2. Click Start > All Programs > SolarWinds Orion > Configuration and Auto-Discovery > Configuration Wizard.
3. Check Database, and then click Next.
    Note: 
If you are prompted to stop services, click Yes.
    To ensure that all updates and changes are installed correctly, it is imperative that you stop all services.
4. Specify the remote SQL Server instance you want to use to store network data, and then provide the credentials, if necessary, to log     into the selected instance.
     Notes:

  • The selected instance must support mixed mode or SQL authentication with strong passwords. A strong password must meet at least three of the following four criteria:
    • Contains at least one uppercase letter.
    • Contains at least one lowercase letter.
    • Contains at least one number.
    • Contains at least one non-alphanumeric character, for example, #, %, or ^.
    • For more information about authentication with strong passwords, see http://msdn.microsoft.com/ms143705.aspx.
  • If you are creating a new database, the user account must be a member of the dbcreator server role. The sysadmin role and the SA user account are always members of dbcreator.
  • If you are using an existing database, the user account needs only to be in the db_owner database role for the existing database.
  • If you are creating a new SQL account for use with Orion NPM, the user account must be a member of the securityadmin server role.

  • Note: The sysadmin role and the SA user account are always members of securityadmin.
  • If you are using an existing SQL account, the user account needs only to be in the db_owner database role for the Orion NPM database.

5. Click Next.
6. If you are creating a new database, select Create a New Database, provide a name for the New Database, and then click Next.
7. If you are using an existing database, select Use an existing database, type the database name or select it from the Existing     Database list, and then click Next.
8. If you want to create a new SQL account for the Orion NPM polling engine and web console to use for accessing the     database, select Create a new account, provide a New Account name and Password, confirm the account password, and then     click Next.
9. If you want to use an existing SQL account for the Orion NPM polling engine and web console to use for accessing the     database, select the Existing Account, provide the appropriate Password, and then click Next.
10. Click Next on the Completing the Orion Configuration Wizard dialog.
11. Click Finish when the Orion Configuration Wizard completes.

 

 

 

 

Last modified
23:59, 22 Jun 2016

Tags

Classifications

Public