We set up a mirrored database system that have three machines (two servers and one arbiter) and the high availability option set up. We are running three windows 2003 servers - one for the primary database, one for the mirror database, and one for the arbiter. We need your help regarding to how to setup the ODBC for our application to connect to primary database.

We plan to have the primary database being use with our application server and the mirror database being use by our reporting server.

In DSN on the Arbiter machine we list-

DSN Name=MyMirrorTest
Server Name =dbserver
Database name=Dbprimary
check TCPIP
entering the hosts (Host=11.2.32.52;Host=11.2.33.53)
Check Shared Memory
Set Liveliness timeout to 7200
Set Idle timeout to 0

Will this setup above work? Are we missing any thing?

Thank in advance for your help.

Best regards,
Rachan Terrell

We were able to set up the ODBC to connect with our database mirroring system using the DSN below.
"Rachan Terrell" <web24by7 (AT) hotmail (DOT) com> wrote

We set up a mirrored database system that have three machines (two servers and one arbiter) and the high availability option set up. We are running three windows 2003 servers - one for the primary database, one for the mirror database, and one for the arbiter. We need your help regarding to how to setup the ODBC for our application to connect to primary database.

We plan to have the primary database being use with our application server and the mirror database being use by our reporting server.

In DSN on the Arbiter machine we list-

DSN Name=MyMirrorTest
Server Name =dbserver
Database name=Dbprimary
check TCPIP
entering the hosts (Host=11.2.32.52;Host=11.2.33.53)
Check Shared Memory
Set Liveliness timeout to 7200
Set Idle timeout to 0

Will this setup above work? Are we missing any thing?

Thank in advance for your help.

Best regards,
Rachan Terrell

With database mirroring you use the -sn switch to specify an alternative server name for both the
primary and mirror databases. You use this alternative server name in the ODBC DSN for connecting to
the primary and if necessary mirror database during a failover.

See:
http://dcx.sybase.com/index.php#http...s-3894811.html

--
Joshua Savill
Sybase iAnywhere - Product Manager


Rachan Terrell wrote:

HOST=x.x.x.1:2638,x.x.x.2:2638
Specify the -sn name in the "Server name:" field on the ODBC Database
tab.
On the Network Tab check TCP/IP and populate field with
User the HOST= IP : Port Comma IP : PORT format


It's tough finding a hint to this, as it is not covered in the
Mirroring section of the documentation.

The following section provides a small Clue however makes no mention
of Mirroring.
Using the Clue provided.
I have tested this by using the "-sb 0" startup switch to insure the
ODBC is not locating the Database by UDP Broadcast.

Books Online
SQL Anywhere Server - Database Administration " Starting and
Connecting to Your Database " Connection parameters and network
protocol options " Network protocol options
http://dcx.sybase.com/1101en/dbadmin...k-conparm.html
Quote:

"
"The following connection string fragment instructs the client to look
for a server on host1 running on port 1234 and for a server on host2
running on port 4567. The client does not look on host1 on port 4567
or on host2 on port 1234.

LINKS=tcpip(HOST=host1:1234,host2:4567)"










On 2 Jan 2009 13:29:39 -0800, "Rachan Terrell" <web24by7 (AT) hotmail (DOT) com>
wrote: