Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
basrizal
Starting Member
1 Post |
 Posted - 2009-03-27 : 04:22:08
|
| Dear All Guys,I need an advice about SQL 2005 mirroring, i need to synchronize 700/instance database (about 50-100 MB/database) from DC to DRC site and make it sync in a realtime manner. I have configured it, but stuck after configuring 31 database mirroring with error insufficient memory ( i have installed SQL 2005 Enterprise Edition on server with 4 socket Dual Core AMD and RAM 32 GB and W2K3 SP 2 OS). My question are:1. Is it possible to make it happen in 1 instance or i need to make multiinstance per server?2. Or any another way to make SQL server sync between DC and DRC in a realtime manner?I really appreciate every advice from you guys.Thanks,BAsrizal |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
basicconfiguration
Constraint Violating Yak Guru
358 Posts |
Posted - 2010-02-11 : 13:40:38
|
| What is a good solution for this question? I'm just curious. |
 |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-02-11 : 13:48:06
|
| Technically, you can have 32,767 databases per instance, but I wouldn't want more than 60 or 70 on any instance.On 32 bit systems, shouldn't mirror more than 10. That's a rough figure.Here is a useful recent article: http://sqlcat.com/technicalnotes/archive/2010/02/10/mirroring-a-large-number-of-databases-in-a-single-sql-server-instance.aspx |
|
|
|
wildstyle
Starting Member
5 Posts |
Posted - 2010-02-22 : 06:45:46
|
| If you have a small amount of databases ( less than 50 ) then database mirroring or log shipping is viable.if you have 700 !! then you have to start looking at a solution that will be stable and supportable. It is POSSIBLE to use log shipping or mirroring for this scenario but not advisable due to the processor overhead as well as the IO overhead on the server. Also, it will be unsupportable when you start to have issues with the solution.Every time i have come across this scenario, we have used SAN mirroring plus geo dispersed clustering to resolve it. It is a simple and elegant solution that does have its issues (cost,vendor tie,monitoring and testing) but for any serious production SQL environment, its the only one that makes me stay highly confident that when i need to use DR, it will work and can be online quickly. I have used this solution with sql 2005 and 2008.regardsGavin |
|
|
|
|
|
|
|
|
Mirroring 700 database per SQL instance