Register an Amazon RDS for SQL Server database instance
Complete the following tasks to register an individual Amazon RDS for SQL Server database instance for monitoring with DPA.
Identify the privileged user
When you register a database instance with the registration wizard, you must provide the credentials of a privileged user. During registration, the privileged user either creates the monitoring user or grants the required privileges to an existing user that you designate as the monitoring user. DPA does not store the credentials of the privileged user.
For self-managed SQL Server database instances, the privileged user requires the following privileges:
To register an instance without granting the
SYSADMIN role, see Register an Amazon RDS SQL Server instance for DPA monitoring without the sysadmin role.
Complete the registration wizard
- On the DPA homepage, click Register DB Instance for Monitoring.
- Under Amazon RDS, click Amazon RDS for SQL Server.
- Click Next.
- Complete the wizard panels as described in the following sections.
If registration fails because your DPA server cannot connect to the instance's server, see DPA database registration failure when attempting to register a database on an external network.
Enter the server name or IP address and port.
DPA monitors all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.
SSL is requested by default. If the server does not support SSL, a plain connection is used.
Enter an Amazon RDS Master User for DPA to register the database instance. If you do not want to enter the Master User that created the database instance, use the SQL statement below to create a new Master User. Replace
dpa with the new user name.
CREATE LOGIN [dpa] WITH PASSWORD=N'Password1'; GRANT ALTER ANY LOGIN TO dpa; GRANT VIEW SERVER STATE TO dpa WITH GRANT OPTION; GRANT VIEW ANY DEFINITION TO dpa WITH GRANT OPTION; GRANT VIEW ANY DATABASE TO dpa WITH GRANT OPTION; ALTER SERVER ROLE [processadmin] ADD MEMBER [dpa];
|Enter the Monitoring User||
Create or specify the account that DPA will use to gather information. To ensure that the account has the required permissions, SolarWinds recommends creating a new account.
To create a new account:
To specify an existing account:
You can also authenticate using a Windows Computer Account.
For SQL Server authentication, only the user name is required. Do not specify a domain.
|Oracle Repository Tablespace||
If your repository database is not Oracle, the wizard skips this step.
Choose the tablespace in the repository database to store DPA performance data for this monitored instance.
By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.
|Select the Alert Groups||
If you have no Alert Groups set up, or if this new database instance does not match the database type of the Alert Group, the wizard skips this step.
Alert Groups simplify alert configuration and help make alerting more consistent across the monitored database instances.
Select the Alert Groups you want the new database instance to join.
|Summary||Review the information and click Register Database Instance.|
|Database Instance Registration Complete||Click Finish to return to the DPA homepage.|
If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.