System design issue with different data src. Please advise.

[User]

Hi everyone,

Right now, one of our client have an in-house system which stores customer
profiles / data.

We are building an external web based system for them which also houses the
same
customer profile/data.

Problem is that the customer's profile data from the web based system must
also be synchronised with the in-house system and vice versa.

The web based system is built on ASP.NET 2.0. We do not have any information
about their in house system except that it is a desktop software

As of now, there are a few solutions i can think of but there are pitfalls
which i'm not able to overcome. Can anyone give some kind advise?

Suggestion 1:
Web based system, we can extract the profile to CSV format and upload it to
the inhouse system end of the day;
every morning, inhouse system will extract their profile to CSV and upload
to the web based system

IMO, i feel this is rather silly. Also, how do we ensure which version of
the data is the latest?

Solution 2:
One centralised datasource.
Get a SQL SERVER host on the public WWW with encrypted connection. Both the
web based software and inhouse system will save to this SQL SERVER. Every
UPDATE statement will invoke a TRIGGER to create a detailed change log on
the customer's profile. This SQL SERVER will also parse out cust profile as
XML.

Or are there any better solutions?

Please advise.

Thanks



Posted Via Usenet.com Premium Usenet Newsgroup Services
----------------------------------------------------------
** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
----------------------------------------------------------
http://www.usenet.com