[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 292
  • Last Modified:

One-database limit on database mirroring?

A colleague has suggested that SQL 2005 database mirroring only supports one database per server. I cannot find any reference to this limitation but want to make sure. Was it a limitation on the original release or perhaps even a beta release?


Thanks

0
AaronAbend
Asked:
AaronAbend
  • 3
2 Solutions
 
imran_fastCommented:
No its not true

but mirroring will be one on one. means one database will be mirrored to one database.
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
he probably means that you cannot mirror the database to the same server/instance.

0
 
imran_fastCommented:
Multi-Database Issues
Many applications make use of multiple databases on a single server. One application may reference multiple databases, or perhaps many applications all make use of several databases. However, database mirroring works with a single database at a time. You need to take this into account when designing mirroring into your database architecture.

If you desire the High Availability mode, your best fit will be when one application matches up with one database. Then if an automatic failover occurs, the application no longer requires any databases on the principal server. Consider what might happen if you have multiple databases on a single server and operate in the High Availability mode. If there is a physical server outage, a SQL Server instance failure, or a communication failure, all the databases would automatically fail over to the standby server, and their mirrors would then become new principal databases. If the witness is visible, the application could connect to the new principal databases. But what would happen if one of the databases incurred a torn page from a disk fault, so that only the one database failed over? In that case, it might be impossible to get the application to connect to all the right databases.

Therefore applications that rely on multiple databases will not be good candidates for the High Availability mode of database mirroring. You may be able to use safety OFF, with the realization that you will not have automatic failover, but you will have a high-performance method of keeping another database server in sync.
0
 
imran_fastCommented:
The above topic shows you can do mirroring on multiple database per server but it is not recommended to do mirroring when your application spans multiple database.
0
 
AaronAbendAuthor Commented:
I found a powerpoint from a Microsoft presentation with the words "High availability for a single database" but the audio indicates that mirroring is done  on a "database by database basis" as distinct from a "server by server" basis. I think this is the source of the confusion. I think Imran's answer is best. Thanks for the quick reply.

for the benefit of those who find this thread... here is the Microsoft presentation with that slide...
http://msevents.microsoft.com/cui/WebCastEventDetails.aspx?EventID=1032282290&EventCategory=5&culture=en-US&CountryCode=US

and here is a discussion of mirroring multiple databases
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx#ECMAE 


0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now