|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Our organization has a medical application that is dependent on 6
independent SQL databases that are loaded on 1 SQL 2005 server/instance. Can a "SQL 2005 High Availability Database Mirror" be used to mirror all six databases and automatically failover. If I have understood correctly, SQL 2005 database mirroring can only be used to failover 1 database due to its inability to synchronize multiple databases. Is that correct? Thank You for your , yukon727 |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
On Sep 30, 6:52 pm, "yukon727" <yukon...@hotmail.com> wrote:
> Our organization has a medical application that is dependent on 6 > independent SQL databases that are loaded on 1 SQL 2005 server/instance. > Can a "SQL 2005 High Availability Database Mirror" be used to mirror all > six databases and automatically failover. > If I have understood correctly, SQL 2005 database mirroring can only be used > to failover 1 database due to its inability to synchronize multiple > databases. Is that correct? > Thank You for your , > yukon727 Hi Yes you are quite correct - mirroring is configured on a 'per database' basis. That doesn't mean that you can't have all 6 databases mirrored independently, but if you had a failure of one database, only that one would failover to the mirror and the remaining 5 would continue to function on the principal server. If your application can handle having connections pointing to multiple datasources, then thats no issue but if, for example, you have queries that span these databases then this is not a viable solution. If you were to use DB mirroring on the premise that you are planning for failover in the case of losing the entire server, then there isn't a problem. However you would always have to live with the risk of a single database failure. |
|
![]() |
| Outils de la discussion | |
|
|