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 |
|
DaPotato
Starting Member
4 Posts |
 Posted - 2008-07-05 : 10:31:40
|
| Hello! I am looking into setting up Database mirroring so I have been doing lots of research. We are only interested in doing automatic failover during the business day. If the principle server goes down at night I don't want the database to auto failover to the mirror. What is the best way to make this happen? The only solution I can see is to create a job that removed the witness in the evening then another job to add the witness back in the morning? Maybe I am approaching this the wrong way. The issue we have is that our Principal server is larger (more RAM more CPU) then our Mirror. So I would rather have the application running off the principal at all times. I could see the situation where updates (reboot) or network maintenance would cause the principal to go off line after our business hours. If this happens after hours I don't want the DB to failover to the mirror. Thanks for any advice! |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-05 : 22:49:05
|
| I think cluster may work better in this case. |
 |
|
|
DaPotato
Starting Member
4 Posts |
Posted - 2008-07-06 : 13:02:29
|
quote:
Originally posted by rmiao
I think cluster may work better in this case.
From what I understand clustering is for the entire server. We have several other databases on the principal server that we would not want to mirror to the backup server. Is there a way to have clustering on a per database basis other then creating another SQL Server instance? |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-06 : 13:16:51
|
| No you can't. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-07 : 10:06:03
|
| Then why don't you go with asynchronous Database mirroring |
|
|
|
DaPotato
Starting Member
4 Posts |
Posted - 2008-07-07 : 11:08:06
|
quote:
Originally posted by sodeep
Then why don't you go with asynchronous Database mirroring
I need to have the automatic failover during business hours, didn't think that was possible with async mirroring. How do guys handle normal server reboots with automatic failover? |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-07 : 11:30:57
|
| I don't understand that if your mirror server can't take load of principle server, then why you are going for automatic failover. You can stop DBmirroring and apply transaction log back in mirror server in Norecovery and start mirroring again. |
|
|
|
DaPotato
Starting Member
4 Posts |
Posted - 2008-07-07 : 12:01:58
|
quote:
Originally posted by sodeep
I don't understand that if your mirror server can't take load of principle server, then why you are going for automatic failover. You can stop DBmirroring and apply transaction log back in mirror server in Norecovery and start mirroring again.
I didn't say that it could not handle the load, just that my principle is a larger server so I would rather have the db run their. I think I can just pause the mirroring during the off hours since there really won't be any activity during those hours anyway. |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-07 : 12:04:06
|
| Donot pause Mirroring as it can fillup Tran log . |
|
|
|
|
|
|
Mirroring - Auto Failover during Scheduled Time