In the Select a SQL Server section of the Register a SQL Server wizard, specify the Server Type you want to add to IDERA SQL Secure for auditing.
Monitoring Always On Availability Groups
Users can monitor Always On Availability Groups using IDERA SQL Secure. Note that instead of monitoring the listener, you must monitor each individual node of the Availability Group. This is because the security configurations for each of the different nodes of the Availability Group are not always identical and monitoring only the listener could possibly leave gaps in the security check.
To specify an instance:
- Select the type of server you want to audit. Available options include:
- On-Premise SQL Server
- SQL Server on Azure Virtual Machine
- Azure SQL Database
- SQL Server on Amazon EC2
- Amazon RDS for SQL Server
- Type the name of the instance you would like to audit. IDERA SQL Secure supports multi-part server fully qualified domain names entered in the following format: name.server.secure.database.net
or click the ellipsis button
to access a list of monitored SQL Servers in your domain, browse to locate your respective instance, then click OK to add it. This feature is not available when working with Azure and Amazon VMs or databases. - Specify the port number, the default port number (1433) or set the port number you configured on the Instance you are registering.
- SQL Secure includes two registration options to secure connectivity between client and server, available for all server types:
- Encrypt connection: Need the same certificate to be installed on the client and server machines. For more information click here.
Trust Server Certificate: When user selects this option do not need any certificate to continue with the registration.
The certificate is created on the server machine once Encrypt Connection option is selected on SQL Server, you can export and import the certificate to the client machine.
5. Click Next to go to the following section and Specify your connection credentials.
You can add as many instances as your SQL Secure license provides. For more information, see Managing Your SQL Secure Licenses.