November 28, 2003 at 8:07 am
I am trying to find the best solution for synchronising a number of databases across many locations with one central SQL server. Each of the databases (Access/Paradox/SQL Server) broadly holds the same information but in bespoke datastructures.
If possible I need to leave those alone because other applications are running from those databases at those locations. However, I have to find some way to sync the data in those tables with this one database (centrally) and then distribute changes through to all the other databases as well.
I have looked at replication - but this seems to be ok if the datastrcutures are identical. If I were to use replication how would I map the columns such that, for instance, the "firstname" field in the central database relates to the "name1" field in (one of) the external databases?
Any idea what the best practice for something like this would be?
November 28, 2003 at 8:50 am
IN heterogenous subscribers you can trasnform the data to be published before inserting it into subscriber.
You can execute a DTS package to get any transformation.
November 30, 2003 at 11:06 am
I believe you would be better staying out of replication in that case and try to tackle it with DTS. Chances are that the structure of those can and will change then you would have to deal with two things the repl and DTS instead of one(DTS).
* Noel
December 1, 2003 at 3:48 am
That's fantastic news.
Are there any online resources/books you could point me to that would guide me through this?
Thanks
quote:
IN heterogenous subscribers you can trasnform the data to be published before inserting it into subscriber.You can execute a DTS package to get any transformation.
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply