![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Hi fellow, I'd like to know if is it possible to configure SQL Server in a cluster enviroment to provide failover, without using shared disks or external |
|
What I wish is setup and cluster to provide failover in case of a hardware malfuction only between servers A and B. The data "integrity" |
|
Anyone knows if this is possible? Cheers, Eric. |
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Hi Michel, The replication and log shipping solves the problem of keeping data between servers ok, but my point is related to the client. Is there a way to make the client service start using the second server automatically in case of server A failure? For example, my apllication use |
|
Cheers, Eric |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
Nope to the original question and no even to database mirroring. If using replication or log shipping, you will have to write code into you application to detect it, redirect, and reconnect. When Yukon ships and if database mirroring is in the product, when the primary fails, you will be disconnected. You will then have to reinitiate the connection. You just won't have to redirect to a different server name. -- Mike Principal Mentor Solid Quality Learning "More than just Training" SQL Server MVP http://www.solidqualitylearning.com http://www.mssqlserver.com |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
Yes, there is supposed to be client library awareness. The feature is currently called "transparent client redirect". The transparent redirect part is that an application doesn't need to change names. It is called "redirect". It is not called "reconnect". The information is in the PASS session you refer to. The same basic information with a few extensions is also contained in a database mirroring session I did in London at DevWeek as well as in Vienna at XtremeSQL. There is also a very big word of caution here since this has the potential to head the wrong direction. Yukon is still in Beta 1. Beta 1 is still NDA. The only thing allowed to be discussed is what is publicly released. Outside of that, there are a small group of people authorized to talk about it. At this point, it is best to not even discuss Yukon features or functionality. If there are specific questions on Yukon, they can be asked in "other venues". -- Mike Principal Mentor Solid Quality Learning "More than just Training" SQL Server MVP http://www.solidqualitylearning.com http://www.mssqlserver.com |
![]() |
| Thread Tools | |
| Display Modes | |
| |