Multiple idatabase registration update#
Multiple idatabase registration registration#
Multiple idatabase registration trial#
Multiple idatabase registration windows#

Under Self-managed, select Microsoft SQL Server.In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.To ensure that the connected user has all the privileges needed to create the monitoring user, SolarWinds recommends connecting as sysadmin to run the script.

Multiple idatabase registration update#

Edit the script to update the user name and password values.Ĭonnect to the SQL Server database instance and run the script.

If default system roles have been altered, DPA Support cannot help you find all items that are assumed to be allowed. These scripts are valid only if the default SQL Server permissions for system roles such as have not been altered with items revoked.

Copy one of the following scripts to a file:įor a SQL Server 2014 or later instance: CreateMonUserSqlServer2014orLater.sqlįor a SQL Server 2012 instance: CreateMonUserSqlServer2012.sql.

To create the monitoring user without the sysadmin role, run a script: For more information, see Create the DPA monitoring user for SQL Server and Azure SQL Managed Instance. To avoid the limitations listed above, create the monitoring user manually and grant the sysadmin role to that user. Register a SQL Server database instance and create the monitoring user yourself Task 1: Create the monitoring user To use this option, see Register a SQL Server database instance and let DPA create the monitoring user below.

The monitoring user is assigned the sysadmin role.ĭPA does not store the user credentials.You must provide the credentials of a user with the sysadmin role so that DPA can create or configure the monitoring user.To use this option, see Register a SQL Server database instance and create the monitoring user yourself below.ĭPA will create/configure the monitoring user. The 'Windows Service Not Running - SQL Server' alert does not work.įor detailed information about the privileges granted to the monitoring user, see this article.The 'SQL Server Log has Many Virtual Logs' alert does not work.DPA cannot collect near-zero or zero cost plans.Because the monitoring user is not granted the sysadmin role, DPA has the following limitations: If you create the monitoring with one of the scripts provided, the DPA monitoring user is not assigned the sysadmin role. You are not prompted to enter privileged user credentials into DPA. Then you use the wizard to complete the registration. With this option, you can create the monitoring user manually or by running a script. I will create the monitoring user manually. If DPA is integrated with CyberArk, these options are not displayed.

Multiple idatabase registration registration#

If DPA is not integrated with CyberArk, the following options in the registration wizard determine how the monitoring user and utility package are created or configured. The DPA monitoring user enables DPA to monitor a database instance.

Multiple idatabase registration trial#

After the trial period, you must activate a license to monitor the database instance. If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately.

Multiple idatabase registration windows#

To register SQL Server database instances using a Windows Computer Account (such as a Network Service Account), see this KB article.įor DPA to collect metrics from a monitored SQL Server instance, Azure SQL instance, or ASMI, the SQL option NUMERIC_ROUNDABOUT must be set to OFF. If you are monitoring a SQL Server Availability Group (AG), see Registration and licensing options for clustered environments. Alternatively, you can use mass registration to registrations to register multiple database instances, or you can register database instances using scripts that call the DPA API.