August 10, 2004 at 6:03 pm
We connect to an external Basis database and update our SQL data once an hour. This works fine except we'd like to update the SQL data more frequently and only include transactions that have been added or changed. We then would like to be able to replicate the data and publish it in a snapshot format once the data is updated. Any help with any of this would be appreciated.
August 11, 2004 at 4:26 am
If you are looking at updating a sql server db from a non sql server db, message queues are required. For example, msqseries. This takes care of changes as they happen one by one. However, it is going to cost you.
There are many ways you can achieve your goal. You can set something up in the basis db to put all dml statements into a seperate table and use this to update the sql db. I do not know if this is possible on basis as I have never used it.
Another way would be to use a data driven query task in a dts package, but they are slow.
With regards to replication, you may be able to use sql server replication between the source sql db and the replicant. I have nver used it, so I cannot comment. Alternatively, have a data driven query tasks from source to replicant.
August 11, 2004 at 11:54 am
An alternative to the Data Driven Query task is to copy the external data to temporary staging tables then use TSQL in Execute SQL tasks to find the new and updated data and insert or update your SQL tables.
Greg
Greg
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply