AvailabilityGuard™ collects Microsoft SQL Server configuration data by connecting through JDBC to each server instance master database and querying system tables.
AvailabilityGuard™ automatically discovers database instances, including virtual IP addresses and non-default ports, subject to scanning the operating system hosting the instance.
To scan a Microsoft SQL instance, you should make the following preparations:
- Identify the instance virtual IP (name or address) - if not automatically discovered.
- Identify the instance connection port - if not automatically discovered.
- Obtain a user account on each instance. AvailabilityGuard supports both Windows authentication and MS-SQL authentication.
Note: Take care to learn in advance which authentication will be used as you will need to specify it when configuring the scan.
- When using Windows Authentication, make sure that the AvailabilityGuard™ collector server is a member of the same domain as the scanned MS SQL Server. In addition, make sure that the user used for scanning the database has login privileges on the AvailabilityGuard™ collector server.
- In order to scan MS SQL Always On, make sure that the user configured to scan this SQL instance has 'View server state' permission.
- Verify that IP connectivity through JDBC (default port 1433) is available between the AvailabilityGuard™ collector server and the target instance.
- Last, configure the connect permission for each database hosted on the server (map the user to all databases).
The following SQL creates a login with the appropriate permissions:
- You will need to GRANT CONNECT for each new database added.
- When you create a user account for scanning, connect using an admin user account.