To register a SQL Server database for DPA to monitor:
Enter the server name or IP address and port. The default port is 1433.
SolarWinds DPA will monitor all databases within the instance. If more than one instance exists on the server, you must register each instance separately in DPA.
Enter SYSADMIN credentials for SolarWinds DPA to register the database instance.
SSL is requested by default. If the server does not support SSL, a plain connection is used.
Are you receiving errors? See DPA for SQL Server installation troubleshooting.
SolarWinds DPA gathers information through this user from the monitored instance.
You can create a monitoring user through DPA, or use an existing user.
SolarWinds recommends this method because SolarWinds DPA requires special permissions that existing users may not have.
Do not specify a domain in the User Name field. Only the user name is required.
Enter an existing Windows user. DPA cannot create a new Windows user for you. If you want to use a new Windows authentication user, you must first create it in your network domain.
Use the syntax
DOMAIN\username in the User Name field.
You can also authenticate using a Windows Computer Account.
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.
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.