Submit a ticketCall us

Announcing NPM 12.2
With NPM 12.2 you can monitor your Cisco ASA firewalls, to monitor VPN tunnels for basic visibility and troubleshooting tunnels. NPM 12.2 also uses the SolarWinds Orion Installer so you can easily install and upgrade one or more Orion Platform products simultaneously.
See new features and improvements.

Home > Success Center > Network Performance Monitor (NPM) > Locating your Orion database properties and storing your DB files

Locating your Orion database properties and storing your DB files

Created by Malik Haider, last modified by MindTouch on Jun 23, 2016

Views: 1,195 Votes: 1 Revisions: 26

Overview

This article describes how to find the Orion DB files location, and provides the recommended best practice to store your database files for optimum performance in a production environment .  

This article is part of the Quick Orion Database Health Check Guide.

Environment

  • NPM 10.0 and above 

Steps

  1. Open the SQL Server Management Studio. 

    You can download a free trial version from the Microsoft Developers Network website

  2. Connect to your SQL database server.

    In the Connect to Server window, complete the fields and click Connect.

  3. In the Microsoft SQL Server Management Studio window, open your Orion Database properties.

    In the Object Explorer, right click the Orion database and select Properties. 

  4. In the Database Properties window, view the files and their locations. 

  5. Ensure that your DB files are stored properly

Storing your DB files

SolarWinds does not recommend storing all DB files on a local drive (C;\ drive) or single disk array within a production environment. However, you can divide the load between multiple disks to balance the load between the arrays. 

Store all DB files on a local drive or single disk (not recommended)

The following table lists the database name and its corresponding file ID, and file name for this configuration. Note that all databases are stored on the D:\ drive. 

Name

File ID

File name

Oriondb

1

D:\Program Files\Microsoft SQL
Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb.mdf

Oriondb_log

2

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb_log.ldf

Oriondb_FG1

3

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb_FG1.mdf

Oriondb_FG2

4

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb_FG2.mdf

Oriondb_FG3

5

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb_FG3.mdf

Oriondb_FG4

6

D:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\Oriondb_FG4.mdf

Divide the load between multiple disks (recommended)

 

The following table lists the database name and its corresponding file ID, and file name for this configuration. Note that all databases are stored on multiple drives. 

Name

File ID

File name

SolarWindsOrion

1

E:\data01\Data\SolarWindsOrion.mdf

SolarWindsOrion_log

2

F:\Log\SolarWindsOrion_log.ldf

SolarWindsOrion_FG1

3

D:\data01\Data\SolarWindsOrion_FG1.mdf

SolarWindsOrion_FG2

4

D:\\data01\Data\SolarWindsOrion_FG2.mdf

SolarWindsOrion_FG3

5

E:\\data01\Data\SolarWindsOrion_FG3.mdf

SolarWindsOrion_FG4

6

E:\data01\Data\SolarWindsOrion_FG4.mdf

SolarWindsOrion_log_2

7

T:\Log\SolarWindsOrion_log2.ldf

 

 

Last modified
22:38, 22 Jun 2016

Tags

Classifications

Public