Hello Guys,

I would appreciate if you can provide me step by step configuring Witness
Server for Database Mirroring.

Quick question, let's say we have three Servers.

DBServer1
DBServer2
Witness1

We would like to create database mirroing from DBServer1 ---> DBServer2 and
witness1 Server reposonsible for failover.

The question here is application point to which Server, Witness1 or DBServe1 ?

If DBServer1 goes down we have to manually change the application connection
string to DBServer2?

Please advice.

Thanks

please follow this to configure mirror server

1. Connect to the instance hosting the main database that you plan to
use as the principal database.
2. Right-click the main database and choose Properties.
3. Select the Mirroring page.
4. Click Configure Security to launch the Configure Database Mirroring
Security
Wizard.
5. On the first screen, the splash screen, select the Do Not Show This
Starting Page
Again check box. Click Next. You will now define endpoints for all three
database mirroring roles: principal, mirror, and witness.
6. On the Include Witness Server page, verify that Yes is selected. This
option
enables you to configure an endpoint’s security for the witness server
instance.
Click Next.
7. On the Choose Servers To Configure page, you see that the Principal Server
check box is selected and unavailable because it is assumed that you are
running
the wizard from that instance. Verify that the Mirror Server Instance and
Witness
Server Instance check boxes are also selected. Click Next.
8. On the Principal Server Instance page, by default, the Principal Server
instance is already selected. In the Listener Port text box, specify a port
number. In the Endpoint Name text box, type a name for the endpoint. Also
verify that the Encrypt Data Sent Through This Endpoint check box is selected
to ensure secured communications. Click Next.

9. On the Mirror Server Instance page, click Connect, specify the instance
name
and login credentials for the instance on which you want to host the mirror
database, and then click Connect. This creates a connection to the instance
hosting
the mirror. Specify the port number and a name for the endpoint, and select
the
Encrypt Data Sent Through This Endpoint check box to ensure secure
communications. Click Next.
10. On the Witness Server Instance page, connect to the witness server
instance the same way you connected to the mirror instance in step 9. Specify
the port number and endpoint name, and then select the Encrypt Data Sent
Through This Endpoint check box to ensure secure communications. Click Next.

11. On the Service Accounts page, you specify service accounts. This step is
optional.

If all the instances that you are configuring endpoints for have the SQL
Server
service running under the same service account, you do not have to specify
anything here. Otherwise, specify the service account for the SQL Server
service on all three instances. Click Next.

12. On the Complete The Wizard page, review the configuration settings that
the
wizard will implement. If you have any changes to make, click Back until you
reach the appropriate page and then make the necessary changes. If the
configuration is correct, click Finish.

13. When the wizard completes, click Close. Click OK to close the Database
Properties message box. This message box serves to remind you that mirroring
does not begin until you click Start Mirroring on the Mirroring page of the
Database Properties dialog box for the primary database. Click OK to close
the Database Properties


also sql server native client can save mirroring information . it means if u
are using sql server native client then your application is automatically
compatable with db mirroring .

manpreet singh
MCITP (DBA,DB Dev)

Rogers" wrote:

Thanks..

"Manpreet Singh" wrote:

I have a similar question regarding connection strings for BizTalk

If I failover, do I manually have to go in and change the BizTalk config
files? Is biztalk compatible with db mirroring?

"Manpreet Singh" wrote:

On a side note, once you get the witness configured you might find when you
have a "hickup" in your network the witness will take that as a failure.
The next thing you know you are running your production systems off of the
mirror. So I would watch the mirror closely after you get it configured.

SQL Squirrel
http://www.lockergnome.com/sqlsquirrel/

"greg" <greg (AT) discussions (DOT) microsoft.com> wrote