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 |
|
sunsanvin
Master Smack Fu Yak Hacker
1274 Posts |
 Posted - 2008-08-05 : 03:06:38
|
| Dear Experts,i'm working with an environment with 2 servers running transactional replication, and another server running with all the web services.around 250 client machines will connect to the databse server. if something goes wrong with the production server, then we need to change the IP address of all the client machines to the replicated server IP.i thought Databse Mirroring is the secondary option for this. if some thing wrong with the production server, there will be no need to change anything at client machines, instead, automatically the clients will connect to the mirrored server. am Correct?if this is correct, i'm going to stop the replication and configure Mirroring. please let me know i'm correct or not?if this is Ok, can i use the mirrored databse for reports purpose? or i need to configure replication in the same server to another databse? please think about my environment and give me the best solution.ArnavEven you learn 1%, Learn it with 100% confidence. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2008-08-05 : 03:24:37
|
| That's automatic failover. For automatic failover you will need a third server as a witness.You have one server principal, one server mirror and one server witness.On failure the mirror becomes principal automatic. If you start again the the old principal after correction of that failure it becomes automatic a mirror.If you don't want to change anything of the clients they have to use SQL Native Clients or .NET Framework 2.0 for SQL Server.WebfredEdit: For report purpose i don't know... |
 |
|
|
|
|
|
Database Mirroring or Replication