RE: [aus-dotnet] Replication.....in dotnet

[anthony]

Title: Message

I talking about the database....   Website A would use database A   Website B would use database B   yes. but if website A is down and everyone uses website B..i will have to migrate all the changed data back to website A when back online...

---

From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of jmplun
Sent: Friday, 3 December 2004 11:57 AM
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Replication.....in dotnet

are you talking the web server here and the database server?   if the database server, regardless of where it is hosted you will need to keep your data in synch. If keeping data in synch not a problem, all you should have to do in web based application is try the database connection. if it fails, then try the other one..   or do I misunderstand the question?   Jarrad

-----Original Message-----
From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of anthony
Sent: Friday, December 03, 2004 11:49 AM
To: dotnet@xxxxxxxxxxx
Subject: RE: [aus-dotnet] Replication.....in dotnet

But this still relies on sql being setup in replication..if i am using different hosting providers i cannot set this up.   Hoping there was technique to do this without relying on the database to do it.  

---

From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf Of Aaron Bull
Sent: Friday, 3 December 2004 11:39 AM
To: dotnet@xxxxxxxxxxx
Subject: Re: [aus-dotnet] Replication.....in dotnet

Sql replication ?

----- Original Message ----- From: anthony To: dotnet@xxxxxxxxxxx Sent: Friday, December 03, 2004 10:48 AM Subject: [aus-dotnet] Replication.....in dotnet
Has anyone had any experience with setting up a system where data can be entered from separate locations.   I am deciding whether i should be using GUIDs or some other technique so i can provide a redundancy layer for my web application.  If my website goes down i want a another database to take over.       Anthony