Web services or something else?

  • Thread starter Thread starter Mateo
  • Start date Start date
M

Mateo

HI!



Situation:

I have database on desktop computer (lets' call it DB1) which is connected
to the internet (permanent ADSL or cable).

I have second database (let's call it DB2) on web server (rented hosting).

I need to synchronise those 2 databases. Syncronisation must be
bidirectional.

Every change in both database have to be synchronised immediately!



I'm asking, what is the best koncept to do this? Web service on the web
server side? Two web services, one on each side? Something else?



When desktop app makes some specific changes in DB those changes must be
sync at that momment with internet DB.



Both DBs are Access, and they will be SQL server in the future, but not yet.



Please advice!

Thx!
 
Mateo said:
HI!



Situation:

I have database on desktop computer (lets' call it DB1) which is connected
to the internet (permanent ADSL or cable).

I have second database (let's call it DB2) on web server (rented hosting).

I need to synchronise those 2 databases. Syncronisation must be
bidirectional.

Every change in both database have to be synchronised immediately!



I'm asking, what is the best koncept to do this? Web service on the web
server side? Two web services, one on each side? Something else?



When desktop app makes some specific changes in DB those changes must be
sync at that momment with internet DB.



Both DBs are Access, and they will be SQL server in the future, but not yet.
Click to expand...

Please advice!Well, a several ways come to mind. I am not a DBA and don't
know the exact reason for synchronizing, and I am thinking of some best
practice here for the 2 separate databases.

1. Perhaps simply a linked access table (to the server database) wold
be best.

2. If the desktop database is still Access, perhaps the desktop goes
thru a Facade; a service (XP/NT) or webservice that hides the
complexity and that will update both at the same time.

2.1. Have a Facade or service/web service doing the updates to both
Databases.
On migration to the SQL Servers.

3. Have an update trigger on the first (desktop) database that on
update will fire and update the 2nd database (internet).

4. Have a Tiered component; a Data Access component, DTS task, or
stored procedure update both databases for you.

I like the linked table option, as it really then is only 1 database no
matter if it is Access or SQL Server. Kiss principle.


Theobaldt1, MCSD
 
Thx!

You gave me some usefull thoughts!!


theobaldt1 said:
Please advice!
Well, a several ways come to mind. I am not a DBA and don't
know the exact reason for synchronizing, and I am thinking of some best
practice here for the 2 separate databases.

1. Perhaps simply a linked access table (to the server database) wold
be best.

2. If the desktop database is still Access, perhaps the desktop goes
thru a Facade; a service (XP/NT) or webservice that hides the
complexity and that will update both at the same time.

2.1. Have a Facade or service/web service doing the updates to both
Databases.
On migration to the SQL Servers.

3. Have an update trigger on the first (desktop) database that on
update will fire and update the 2nd database (internet).

4. Have a Tiered component; a Data Access component, DTS task, or
stored procedure update both databases for you.

I like the linked table option, as it really then is only 1 database no
matter if it is Access or SQL Server. Kiss principle.


Theobaldt1, MCSD
Click to expand...
 
Back
Top