The following minimum requirements include the requirements for the BindView RMS® Console and Information Server:

RMS Console

· Pentium® II 450 MHz

· 256 MB RAM

· 300 MB of free disk space

· Microsoft® Windows® 2000 SP3 (server or workstation), Windows XP® Professional SP1, or Windows Server™ 2003 or later

· SVGA monitor that supports 256 colors with the display set to 800 x 600 pixels or greater

· Microsoft® Internet Explorer v5.5 SP1 or later

· Microsoft® Outlook® 2000, Novell® GroupWise® v5.5, Lotus Notes® v5.0 or Lotus Domino (only required for e-mailing export files)

· Microsoft® Excel (required for Excel (using OLE) export files)

· Client for Microsoft® Networks

· Pentium III 800 MHz

· 512 MB RAM

· 500 MB of free disk space

· Microsoft Windows 2000 SP3 (server or workstation), Windows XP Professional SP1, or Windows Server 2003 or later

· Microsoft SQL Server v7.0 or 2000, Microsoft SQL Server Desktop Engine (MSDE) v1.0 or 2000, Microsoft SQL Server Standard Edition v7.0 or 2000, Microsoft SQL Server Enterprise Edition v7.0 or 2000, Microsoft SQL Server Personal Edition 2000, Microsoft SQL Server Developer Edition 2000

· Microsoft Internet Explorer v5.5 SP1 or later

· Microsoft Outlook 2000, Novell GroupWise v5.5, Lotus Notes v5.0 or Lotus Domino (only required for e-mailing export files)

· Microsoft Excel (required for Excel (using OLE) export files)

· Client for Microsoft Networks

· When adding licenses, you may receive the error message: "License XXXX-XXXX is of unknown type. Do you wish to add?" Click Yes to add the license, and the program will continue to run normally.

· After you have installed the Microsoft SQL Server Enterprise Manager, you will need to start the Microsoft SQL Server service before launching and using the bv-Control for Microsoft SQL Server application. If the Microsoft SQL Server service is not restarted, you will receive a critical failure message stating that the SQL server does not exist.

· In this release, while creating a query you cannot add 'All Servers' as a scope in the Query Builder. However, if you have a previously saved 'All Servers' in a named scope and have upgraded to bv-Control for Microsoft SQL Server v8.00 SP1, then the scope will continue to work through that named scope.

· For querying a Microsoft SQL server installed on a Windows XP SP2 machine, only Windows Authentication is supported.

· If you execute a query using the Servers data source, the IsClustered field displays 'Unknown' for Microsoft SQL Server v7.0.

· For the Transaction Logs data source:

· For online transaction logs, the Transaction Summary and Additional Information fields do not show old values and new values for the modify transactions on variable length table columns.

· For online transaction logs, the Transaction Summary field only shows the modified characters in the new value and old value columns for the modify transactions on table columns of string data types.

· The Transaction Summary field does not display values for table columns with user-defined data types.

· For backup and offline transaction logs, the Transaction Summary and Additional Information fields will be empty.

· For backup and offline transaction logs, if read permissions are denied on the transaction log file, the message "No records matched the specified query" will be displayed.

· For backup and offline transaction logs, the following fields will be empty: User Name, Object Name, and Index Name.

· For offline transaction logs the Server Name field will be empty.

· For transactions performed by Microsoft SQL Server, the UserId field value will be 65,536(-1). For backup and offline transaction logs, an incorrect value will be displayed.

· For an offline database, a query on the Databases data source will display the value 'true' for the IsDeleted field.

Change History

The following is a summary of the change history of bv-Control for Microsoft SQL Server v8.00 SP1:

· The following data sources have been overhauled to greatly improve query performance:
· Columns

· Database Permissions

· Stored Procedures

· Tables

· Views

· Evidence fields have been introduced in the Database Permissions data source. Permissions can be granted or denied to a user directly, or through a role, or through a group. Evidence fields help in understanding how exactly a user has been granted or denied a particular permission. To report on how a user has an effective permission, the following fields have been introduced:

· Is Assigned Through Role?

· Is System Object?

· Role Name

· Server Login Name

· User Type


Additionally, the effective permissions field values on the Columns, Tables, Views, and Stored Procedures data sources have been updated to include evidence information for the effective permissions.

v8.00

The following is a summary of the change history of bv-Control for Microsoft SQL Server v8.00:

· Simplified configuration management.

· Ability to include all the visible Microsoft SQL servers as the default scope.

· Ability to use Named Scopes across data sources.

· Ability to filter on the date and time for data sources that have date and time fields.

· Ability to specify Domain Credentials to query all the servers in the domain.

Documentation

The User Guide contains information about bv-Control for Microsoft SQL Server and about the BindView RMS Console and Information Server. If you upgrade the BindView RMS Console and Information Server, you should consult the BindView RMS Console and Information Server User Guide for information about the new version of the Console.

© 2004 BindView Corporation. All rights reserved.