3.6.0 MxDB for SQL Server Installation and Administration Guide (5697-7088, December 2007)

Chapter 5: Configuration and Operation 59
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
Progress Reports
When you perform operations such as creating a Virtual SQL Server,
adding a virtual SQL instance, or moving a Virtual SQL Server to
maintenance mode, a progress report is displayed. The report lists the
tasks required to perform the operation.
Click Run to start the operation. The tasks are checked off as they are
performed. If a particular task fails, it is marked with an X and you are
asked if you want to continue the operation. The progress report provides
two options that can be used if a task fails:
Run. Click this button again to retry the failed task.
Undo. Click this button to undo all tasks in the list and return the
Virtual SQL Server to its original state.
You can also cancel the operation at any time by clicking the Cancel
button. When the task currently in progress has completed, MxDB for
SQL Server will undo each of the completed tasks and the Virtual SQL
Server will be returned to its original state.
Add a Virtual SQL Instance
Each Virtual SQL Server can be associated with up to 16 SQL instances.
You can add all of the primary SQL instances on a node to the same
Virtual SQL Server, or you can create multiple Virtual SQL Servers and
spread the primary SQL instances among them.
When assigning SQL instances to a Virtual SQL Server, you should be
aware of the following:
If you want to use replication on a SQL instance assigned to a Virtual
SQL Server, you will need to define the replication after you add the
instance to the Virtual SQL Server.
If you assign multiple SQL instances to the same Virtual SQL Server,
keep in mind that a failure of one instance can cause the Virtual SQL
Server to fail over. This failover will include all instances associated
with the Virtual SQL Server, not just the failed instance.