3.4.0 Matrix Server Release Notes

PolyServe Matrix Server Release Notes 20

Matrix Database Solution Pack for SQL Server

The following issues affect the Matrix Database Solution Pack for SQL

Server.

Bug

Description

3737 Virtual SQL Server names are not checked against existing

NetBIOS names

When a Virtual SQL Server is created, its name is not checked

against the existing NetBIOS names. Consequently, it is possible

to create duplicate NetBIOS names on the network. This will

cause the Virtual SQL Server to fail when it is started.

Workaround. When you create a Virtual SQL Server, ensure that

the name is not already assigned on the network. A DNS lookup

is performed when the name is entered, but you should also

manually ping the name to ensure that it is not being used.

4046

Virtual SQL Server backup instances may appear in

Enterprise Manager

MxDB for SQL Server does not keep the backup instances from

appearing in the SQL Server Enterprise Manager. These backup

SQL Server instances are not active and should not be selected

for operations.

Be sure to select the active SQL Server instance from within

Enterprise Manager.

4201 DNS [PTR] records are not created automatically for Virtual

SQL Servers

MxDB for SQL Server does not dynamically create a DNS [PTR]

record for the Virtual SQL Server/IP. Thus, DNS reverse lookup

may fail and cause Windows authentication to fail. It is

recommended that you manually create a [PTR] record for each

Virtual SQL Server.