Submit a ticketCall us

WebinarDatabase Roundtable – Expert Database Professionals Feel Your Pain

In this video broadcast, Head Geek™ Tom LaRock is joined by Karen Lopez, Tim Chapman, and David Klee. They’ve known each other for many years, so this discussion was like four friends getting together to talk data and databases. They discussed diagnostic data collection, common performance root causes, reactive tuning versus proactive, and more. Join us for an engaging discussion on these topics! Plus, Tom LaRock will be available to answer your questions live.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > SolarWinds database in Single User mode

SolarWinds database in Single User mode

Created by Matthew Lamb, last modified by MindTouch on Jun 23, 2016

Views: 830 Votes: 0 Revisions: 5


This article addresses the issue where the SolarWinds Orion database is incorrectly placed into a Single User mode state.


  • All Orion Core versions
  • Microsoft SQL Server


This can occur when the database was set in Single User mode by the DBA or forced by the SQL server due to an issue. However, Orion requires it be in a Multi-user mode to allow multiple connections and updates for all the necessary services and servers.


  1. Restart the Microsoft SQL server. 
    Note: This step is needed to clear out whichever user or connection currently has control of the database currently. It is possible to log in as an SA and query all current processes running on that database and kill them, but a reboot of the server will ensure the connection is cut every time, regardless of SQL permissions.
  2. Open SQL Management Studio on the SQL server.
  3. Select the database and click New Query.
  4. Run the following query in the query screen:
    Alter database [Current] SET Multi_USER
  5. Verify that the database is no longer in Single User mode.


Last modified