Using a copy node as an arbiter

If you do not want to create a new database server to run the arbiter of a high availability, read-only scale-out system, you can use an existing copy node of the system instead.

Define the arbiter to refer to a copy node

Create the arbiter server so that its name does not match the server name of any of the database servers in the high availability system. The name of the arbiter server is used solely to identify the arbiter connection string in the mirror server definitions.

Example

For example, there is no database server named TheArbiter in the high availability and read-only scale-out system that uses the following server definition.

CREATE MIRROR SERVER "scaleout_child" 
AS COPY connection_string = 'SERVER=scaleout_child;HOST=winxp-2:6878';
CREATE MIRROR SERVER "TheArbiter"
AS ARBITER connection_string = 'SERVER=scaleout_child;HOST=winxp-2:6878';

Discuss this page in DocCommentXchange.

Using a copy node as an arbiter

Define the arbiter to refer to a copy node

See also

Example