3.6.2 HP PolyServe Software for Microsoft SQL Server release notes (T5392-96040, June 2009)

• Defect 19211. The Multi-Node Installer did not support NTLM authentication.
• Defect 19250. After a Virtual SQL Server was failed over to another node, alerts remained on
the original node.
• Defect 19331. When a duplicate record was entered into the ia.conf file, Instance Aliasing
did not discard the duplicate.
• Defect 19529. The message associated with Event 40161 did not report that Registry Replicator
failed to start replication of the keys.
• Defect 19544. The mx vsq update command could replace the application name with the IP
address for the Virtual SQL Server.
• Defect 19545. When multiple SQL instances were assigned to the same Virtual SQL Server, the
Multi-Node Upgrade wizard incorrectly warned that the SQL instances were included in multiple
Virtual SQL Servers.
• Defect 19612. When Instance Aliasing was started on a node, it did not remove any legacy IPs
that were bound to the node.
• Defect 19627. The user name or domain specified for a SQL Server installation or upgrade could
not contain a period.
• Defect 19803. The registry was not updated when a Virtual SQL instance was upgraded.
• Defect 19830. After a SQL 2005 instance was virtualized, the @@servername property returned
the physical server name.
• Defect 19876. SQL Server installations failed when a custom data path was specified in the tem-
plate file.
• Defect 19892. An virtualized SQL instance migrated from the 3.4 release to the 3.6 release could
not be deleted.
• Defect 20110. An attempt to virtualize a SQL Server instance failed with “System error: the security
identifier is not allowed to be the owner of this object.”
• Defect 20193. The output from the mx vsql status command did not include an enable/disable
column.
• Defect 20334. When a Virtual SQL Instance is revirtualized, a popup message states that the
data files for the instance already exist. The default value for the popup message has been changed
to use the existing data files instead of overwriting them.
• Defect 20428. The mx vsqlinstance add command did not recognize “ default” (or “Default”)
as the name of an instance.
• Defect 20429. The mx vsqlinstance delete command did not recognize “default” (or
“Default”) as the name of an instance.
• Defect 20949. A memory access issue could cause the PolyServe SQL Browser Service to become
corrupted.
• Defect 20951. A collation issue caused a virtualization attempt to fail.
• Defect 21392. When a template file created with the Multi-Node Installer was opened for editing,
it showed checkmarks for features that had been previously unchecked.
Contents of the 3.6.0 Release
The 3.6.0 release includes the following new features:
• New high-availability architecture. See “New Active-Passive Architecture,” below, for more inform-
ation
• The new Multi-Node Install Wizard for SQL Server can be used to install SQL Server 2000 and
2005 instances on multiple nodes simultaneously. New features provided with the installer include:
HP PolyServe Software for Microsoft SQL Server release notes 5