A blog by Jose Barreto, a member of the File Server team at Microsoft.
All messages posted to this blog are provided "AS IS" with no warranties, and confer no rights.
Information on unreleased products are subject to change without notice.
Dates related to unreleased products are estimates and are subject to change without notice.
The content of this site are personal opinions and might not represent the Microsoft Corporation view.
The information contained in this blog represents my view on the issues discussed as of the date of publication.
You should not consider older, out-of-date posts to reflect my current thoughts and opinions.
© Copyright 2004-2012 by Jose Barreto. All rights reserved.
Follow @josebarreto on Twitter for updates on new blog posts.
SQL Server 2005 Database Mirroring is a high availability feature that maintains a duplicate copy of a database (close by or across the globe), keeps it up to date (synchronously or asynchronously) and can even provide automatic failover.
There are other SQL Server technologies that can use be used in similar situations, like database clusters, log shipping and replication. Mirroring is unique because:
Mirroring also has some restrictions and it will not work in every scenario. Here are some of those:
If it sounds interesting, check this step-by-step demonstration of how to configure Mirroring in a set of SQL Servers (you can view it online or download the video for offline viewing):https://www.livemeeting.com/cc/microsoft/view?id=SQLMirroring&pw=josebda
I hope you have the time to check the video. You could also get all the details about the technology, which can be found at:http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx
PingBack from http://www.kaizenlog.com/2007/08/11/database-11082007/