![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(108.80000000000001, 96%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EU%3C/text%3E%3C/svg%3E)
In the context of database mirroring in SQL Server, the mirror database is typically not readable. The mirror database is a copy of the principal database that is used for failover purposes and is generally in a read-only state. This means that users cannot perform read operations on the mirror database while it is in this state.
However, there are configurations where you can set up a readable secondary database using other features like Always On Availability Groups, which allows for read access to secondary replicas. For pure database mirroring, the mirror database is meant to be a standby and is not designed for read operations.
If you want to have a readable database setup, you might want to consider using Always On Availability Groups instead of database mirroring.
References:
- Overview of Database Mirroring
- Database Mirroring Terms and Definitions
- Setting Up Database Mirroring (SQL Server)
- Preparing a Server Instance to Host a Mirror Server
- Overview: Establishing a Database Mirroring Session
- Interoperability and Coexistence with Other Database Engine Features
- Database Mirroring and Replication (SQL Server)
- Database Mirroring and Log Shipping (SQL Server)
- Database Mirroring and Database Snapshots (SQL Server)
- Database mirroring and full-text catalogs (SQL Server)