I would suggest using SQL Server's replication functionality. Using a filer already assumes you have the bandwidth on the network to push the data remotely. Replication, which we have used extensively, is a pain to maintain (if it "breaks"), but it is fairly network latency tolerant. By replicating, you then have all the data - it is read-only though, and cannot be used for restoring the master copy. So, it is not a replacement for using Snapmirror/SnapRestore.
Hope that is useful.
-----Original Message----- From: Chris Good [mailto:chris@g2.nu] Sent: Thursday, March 28, 2002 10:29 AM To: toasters@mathworks.com Subject: Re: multiple SQL servers on mirrored database
""Zekeriya Eskiocak"" zeskiocak@prolink.com.tr wrote in message news:LNECLOKLKNCMJCNPDJEGKELECDAA.zeskiocak@prolink.com.tr...
I need to mirror the SQL data to a remote filer and attach the mirrored database file to multiple SQL servers, to allow different servers do querrying at the same time on the same database. Is this deployment
possible
with SQL Server either 7.0 or 2000? Has anyone done a similar config?
Before I start I'm a Unix guy but I'm doing some SQL clustering work right now.
AIUI SQL server isn't happy out of the box running on a filer. With netapp drivers its ok. Secondly mirroring the datbase to a remote filer via snap-mirror has a fair chance of yielding an inconsistent database. Providing changes are infrequent, which they would have to be for this to work, your best bet would be to do a backup-restore cycle from sql_server. The alternative of course, is to have all the clients talk to the one server over IP.
Chris