Use the mass registration wizard to register multiple instances. When the information is correct, click Register. Review the information on the Summary page. If no alert groups exist, or the existing groups do not match this instance's database type, this option is not shown. (Optional) If you have existing alert groups, you can assign this database instance to one or more groups. If no manual groups exist, this option is not shown. (Optional) If you have manually created instance groups, you can assign this database instance to one of the groups. The Display name field defaults to the name retrieved from the database instance. However, data for monitored instances can be stored in separate tablespaces.Įnter the name that DPA will display to identify this database instance. If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance.īy default, the performance data is stored in the default tablespace of the repository user. The instance name and group membership can be changed after registration. Or, if DPA is configured to use CyberArk, enter the CyberArk credentials query for the monitoring user.ĭPA validates the connection information and the privileges of the monitoring user. The client verifies the certificate chain and also verifies that the server hostname matches its certificate's Subject Alternative Name or Common Name (CN).Įnter the user name and password of the monitoring user created previously. Validate server certificate and match hostname The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA). This SSL configuration does not protect against man-in-the-middle attack because no certificate is required. SSL is enabled, but no server certificate checks are performed. Under SSL mode, specify the type of secure socket layer (SSL) connections established between the instance and the DPA server. Otherwise, enter the server name or IP address and the port number. If the SQL Server Browser service is running, enter the server name or IP address and the instance name in this format: Under Google Cloud SQL, select Cloud SQL for SQL Server.Ĭomplete the Connection information panel:Įnter connection information for the SQL Server instance:.In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.Register Database wizardĬomplete the following steps to use the wizard to Register Database register one instance at a time. You can register the instance using the Register Database wizard, mass registration wizard, or the DPA API. SELECT name FROM where name NOT IN ('master', 'msdb', 'tempdb', 'model') ĬREATE USER FOR LOGIN sp_addrolemember N''db_datareader'', sp_executesql NEXT FROM dbs INTO dbs in case there are databases not accessible by sqlserver user, you need to grant the permissions by the database ownerĭECLARE dbs CURSOR LOCAL FAST_FORWARD FOR create user on each database and grant db_datareader role
assign processaadmin role to allow kill sessionsĪLTER SERVER ROLE ADD MEMBER
GRANT VIEW ANY DEFINITION TO AS CustomerDbRootRole GRANT VIEW ANY DATABASE TO AS CustomerDbRootRole
GRANT VIEW SERVER STATE TO AS CustomerDbRootRole If default system roles have been altered, DPA Support cannot help you find all items that are assumed to be allowed. The following script is valid only if the default SQL Server permissions for system roles such as have not been altered with items revoked. Limitations are described in the following sections. DPA can monitor without them, but the monitoring will be limited. The majority of the permissions are optional. Then run the following script using the default sqlserver or any other privileged account to assign the permissions needed for monitoring. Under Users, create a new user for DPA monitoring.