3.6.0 Matrix Server Release Notes (5697-7087, February 2008)

PolyServe Matrix Server Release Notes 23

4046 Virtual SQL Server backup instances may appear in

Enterprise Manager

When the Instance Aliasing feature is not used, 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.

4432 Management Console shows inconsistent information

The list of available servers on the Add Virtual SQL Server

window may identify some servers by their DNS names and

other servers by their IP addresses. This occurs because either

reverse lookup is not set up or it is still resolving the names.

4846

Error can occur if timeouts exceeded

Under a controlled failover scenario (for example, disabling an

instance via the PolyServe Management Console), the system

will allow 45 seconds for SQL Server and SQL Agent to stop. If it

takes longer than the allocated time to stop these services, an

Alert will appear on the Management Console.

5288

Windows limitation for nodes with 16 instances of SQL Server

If the SQL Server service startup account is a NT domain user

and the node needs to start 16 instances of SQL Server, it will

run out of available desktops.

Workaround. Reduce the third SharedSection value from 512 to

256. See the following Knowledge Base article for details:

http://support.microsoft.com/?id=184802

If the SQL Server service startup account is LocalSystem, this

bug and the workaround do not apply.

5291

Port information is not updated on the Management Console

When the TCP port used by a SQL service monitor is changed

manually, the PolyServe Management Console does not display

the new port number.

Bug

Description