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 |
|
methodology
Starting Member
31 Posts |
 Posted - 2007-08-30 : 09:30:57
|
| Hi,I have a requirement for users to be able to access either the production OR the mirror / replica / hot / whatever server without thetre being a failover situation in place. effectively its a tax dodge - sticking a bunch of servers in country x as a DR solution apparently isnt good enough. we need to be able to use the kit any time we want and to be able to carry out work from wither prod or DR hardware / environsments.SQL mirroring prevents the replica from servicing users requests, as does double take and probably Wan sync and most other stuff I can find. Is there any product / any way I can accomplish this that DOESN'T effectively disable the back end?.both front and backend would need to be readable AND writable, so having some sort of read only thing at the back wouldnt be any good...and there is no way on Gods green earth that I am going down the route of SQL 2005 Replication again, so if that does indeed accomplish what I want - effectively 2 way syncronous multi master writable replicating databases, then i quit.perfectly fine fine for there to be nothing available that can accomplish this...cheers allAlastairMethodology"A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips. |
|
|
methodology
Starting Member
31 Posts |
Posted - 2007-08-30 : 09:34:15
|
| I suppose this would be called SQL data syncronisation rather than H/A or replication?anyone?muchas muchas"A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips. |
 |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-08-30 : 09:53:42
|
| If you have multiple applications with different databases, you could install live databases at each site with failover mirrors at the other site. Each server would be live for at least one application and would be the mirror for other applications.CODO ERGO SUM |
|
|
|
methodology
Starting Member
31 Posts |
Posted - 2007-08-30 : 10:05:09
|
| ok, but that solution doesnt keep two effectively production servers syncronous and accessible at all times..I dont think Im going to be able to this. youd need a mechanism for conflict resolution in realtime and if its a highly dynamic database nothings going to be powerful enough to keep the whole thing running..."A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips. |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-08-30 : 10:21:43
|
| If you really want to do this, I know it could be done with Oracle RDB on a distributed cluster, and maybe with Oracle.However, you would probably spend far more to do it than any possible savings for a tax dodge.CODO ERGO SUM |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-30 : 21:46:28
|
| What one of our app does is writing to both servers at same time, the app will queue transactions if one of the server is not available so doesn't cause transaction failure. |
|
|
|
methodology
Starting Member
31 Posts |
Posted - 2007-08-31 : 03:14:49
|
| hmm yes ok, that would do it.ill suggest it as what I think is the only possible solution to this.Thanks for the suggestion, and thanks to all for their time.AlastairMethodology"A computer once beat me at chess - but it was no match for me at kick boxing" - Emo Phillips. |
|
|
|
|
|
|
|
|
SQL H/A where BOTH servers read & writeable