Like log shipping, database mirroring provides protection on a per-database, not a per-instance, level.
Introduction: This post takes you through SQL Server Database Mirroring with screenshots in both the ways using T-SQL script and management studio.
Also you will learn components involved in SQL Server database mirroring.
The switch to the other database can happen either manually or automatically, depending on your configuration.
Therefore, anything captured in the transaction log will be applied to the copy of the database on the other server.
The action of sending transaction log records can happen synchronously or asynchronously.
Some DBAs need the servers to be available 24/7, while others can afford an outage of a couple of hours. For example, Clustering is an expensive high availability method when compared to Database Mirroring, but it allows the user to failover immediately.Since SQL Server 2000, you have been able to create a standby server using replication, log shipping and backup and restore — but now Microsoft has introduced a built-in tool that enables automated failover.Like log shipping, you take a pointin-time backup of your database and restore it in a state that can load transaction logs.Database mirroring does not work by sending individual transaction log backups—it sends each individual transaction log record to the standby database (like transactional replication, which is covered in the next chapter).Database Mirroring is a new feature in SQL Server 2005 that allows you to mirror database contents from one SQL Server to another SQL Server.It also enables you to failover to the mirrored database in case of a failure.