Robert L. Stewart
rl_stewart at highstream.net
Thu Sep 15 13:24:06 CDT 2005
Billy, Sounds like you will not need to worry about it: MCPmag.com: Database Mirroring Not Ready for Production When SQL Server 2005 Ships When SQL Server 2005 is released to manufacturing in the next few months, Microsoft will take the exceptional step of designating one of its high-profile features as being intended for evaluation only. By Scott Bekker http://mcpmag.com/news/article.asp?editorialsid=846 Robert At 12:00 PM 9/15/2005, you wrote: >Date: Thu, 15 Sep 2005 06:53:32 +0000 >From: "Billy Pang" <tuxedo_man at hotmail.com> >Subject: Re: [dba-SQLServer] sql server 2005 database mirroring - > howmany copies of sql server? >To: dba-sqlserver at databaseadvisors.com >Message-ID: <BAY102-F69929389101A8E6391725E59E0 at phx.gbl> >Content-Type: text/plain; format=flowed > >Hi Jim: > >Not sure if it is publishing or subscribing in this scenario. Are you >talking about (snapshot) replication? > >Database mirroring is new in sql server 2005, which is a bit different than >replication. in database mirroring, there is a principal database, which is >what client accesses. if the principal database is disconnected, the witness >tells the mirror server to become the principal server; the failover is >automatic and transparent to the client; replication is like database >mirroring because there are two copies of the db except that in db >mirroring, the client only sees one database. replication probably good for >WANs; for db mirroring, it is preferred that all servers are on same domain >over standard network infrastructre. > >Billy