The RMS data collector uses the bv-Control for Microsoft SQL Server snap-in module to collect data from Microsoft SQL Server databases. Before you install bv-Control for Microsoft SQL Server, ensure that your workstation and SQL Server environment meet the minimum requirements to run the product.
The bv-Control for Microsoft SQL Server snap-in supports the following Microsoft SQL Server platforms:
To query against Microsoft SQL Server 2005, you must install the SQL Distributed Management Object component, SQLDMO.dll, on the Information Server. You can install the component either separately or from the CCS_DataCollection\Redist folder on the product disc.
The following minimum user rights are required to query the SQL Server:
The user credentials for Windows or SQL Server that are supplied for connecting to the SQL Server must be a user for the SQL Server. Otherwise, the credential verification in bv-Control for Microsoft SQL Server fails.
User credentials for Windows or SQL Server that are supplied for connecting to the SQL Server must have read rights on the master database. This master database must belong to the SQL Server that is queried. Otherwise, the credential verification in bv-Control for Microsoft SQL Server fails.
You should use SSL to encrypt application traffic between the Information Server and the target SQL Server. The bv-Control for Microsoft SQL Server functionality does not require SSL communication to be enabled. The product works seamlessly with the encrypted or non-encrypted protocols to communicate with the SQL Server. The communications preferences are set in the SQL Server client configuration. You should also ensure that your SQL Server is patched appropriately and regularly for any vulnerabilities that are related to the open SQL port.
When you use SQL audits, you may configure bv-Control for SQL Server to collect only the required information. SQL audits can generate large data sets. The large data sets can have an impact on the disk space requirement or the network bandwidth requirements. In addition, the amount of data might degrade SQL Server performance.