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 |
|
supersql
Yak Posting Veteran
99 Posts |
 Posted - 2009-01-18 : 11:50:07
|
| Here is the setup am thinking of , let me know if that is a gud idea. May be again thinking of clustering.I do have 6 servers and only 1 instance on each. each server may have nearly 10 big sql 2005 databases each db of about 700GB on an average.Dev1 Dev2 Dev3 Dev4 Dev5 StageDevdb1 db11 db21 db31 db41 db5db2 db12 db22 db32 db42 db8 . . . . . db21 . . . . . db27 . . . . . db32db10 db20 db30 db40 db50 db45all these servers will be under one name called " DEV" like clustering have 6 nodes. To acheive my purpose i want to update/load data in StageDev\db8 and once update is done for StageDev\db8 then failover(take offline) just one db Dev1\db8 and bring StageDev1\Dev8. I n this process the end user should not be noticed that he was switched from Dev1 to StageDev. Ofcourse 30min downtime may be accepted in this scenario.I am not sure if this setup will workout. If this can be done in that case what hardware/software is needed to make it run smooth. |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-01-18 : 12:33:16
|
| You should use Database Mirroring for it. |
 |
|
|
supersql
Yak Posting Veteran
99 Posts |
Posted - 2009-01-27 : 17:58:49
|
| Hows that possible? I dont want to share resources between the servers like CPU,RAM etc. I am trying to get rid of downtime when users do heavy data load job so that other users can actively work on the servers.thanks |
|
|
|
|
|
|
Sever Setup