Just a quick opinion here... My experience with replication was observing another development team at my old work trying for months to get it right. Not for lack of talent AFAIK - if the system is relatively simple and the volume is not stupendous replication might be ok, but my (relatively uneducated) opinion is that replication, at least in MSSQL, still has a few volume- related problems.
If it's lightweight order update/receipts - might it be worth investigating modifying the client installations to send an XML/ SOAP message to the main db server via a web-server that hosts a SOAP site or webservice that consumes the XML data message sent by your client installations? just a thought ----- Original Message ----- From: "Brendon G" <[EMAIL PROTECTED]> To: "ActiveServerPages" <[EMAIL PROTECTED]> Sent: Thursday, August 15, 2002 4:41 PM Subject: Re: Physically Remote databases : > What type of updating are we talking about? : > Also, what type of database servers? : : I doubt there will be any updating actually i through it to the sentence out : of curiousity. I'm noty sure of the database servers at the moment. I've : sent back a list of questions and that was one of them. So until then... : : It looking like it will just read the status of an order and display it to : the client. : : > If SQL Server, and batch updating, then you could use DTS : > If it needs to be a bit more live, you could have linked servers: one : > publishes data which the other consumes. : : I was thinking along the lines of linked or replicated servers. I guess it : really depends on the database itself more than anything. : : : Cheers : : Brendon : : : : --- : You are currently subscribed to activeserverpages as: [EMAIL PROTECTED] : To unsubscribe send a blank email to %%email.unsub%% : --- You are currently subscribed to activeserverpages as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED]
