SQL 2005 DB mirroring using high availability mode, can it failover to a different server name?

  • Hello,

    This is a SQL newbie question.

    If the 2 SQL 2005 servers are setup as below w/ third instance for witness for auto-failover, would this auto-failover setup work for sharepoint service? I'm wondering since the server names are diffrent, how would it auto-failover from SQL1 to SQL2 for sharepoint? I'm assuming the DB will failover but still need to change the DB server the sharepoint services is pointing to from SQL1 to SQL2 manually on the server (Sharepoint) that's running sharepoint services?

    server name: SQL1

    Instance: default

    DB mirrored: sharepoint_Config, sharepint_AdminContent (principal)

    server name: SQL2

    Instance:default

    DB mirrored: sharepoint_Config, sharepint_AdminContent (mirrored from the principal)

    2nd Instance: SQL2\witness

    servername: Sharepoint (just server running sharepoint services, not running SQL locally)

    DB pointing to SQL1

  • When using mirroring your servers will always have different names. With synchronous or Safe mirroring you can configure auto-failover at the client by defining an alternative server in the connection settings. When the default server is not available, the client will try the second server.

    By the way having the witness instance on the same server as your mirror is not a good idea.

    If the machine needs to be stopped both go down and there's no more quorum left. I suggest you move the witness to another machine. You don't need to worry about costs, since the witness carries hardly any load and SQL Express is sufficient.

    [font="Verdana"]Markus Bohse[/font]

  • Thanks. I didn't know that SQL Express could be used as a witness server.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply