February 17, 2014 at 3:33 pm
We are in the process of replacing an archaic email based solution for extracting data from approx. 100 of our store's POS systems. As part of the project I'm considering using replication for data transfer from the stores to our HQ, and would like to get some opinions on whether it is appropriate in this situation.
We will be using stored procedures at the stores to do daily (or weekly) extracts to work tables, which would then be transferred to HQ where the reporting tables would be updated. The data to be moved is only a subset of the current data. While some of the data is in detail form (i.e., daily sales records header and detail records), other is summary only. The detailed sales records are actually partial extracts from up to 15 different tables from the vendors POS application.
Once the data gets to HQ it would be used to update the live tables. If any data received is already on the HQ machine, it would be deleted first thus replacing any data that is being resent for any reason, such as sales records, or summaries, that have had subsequent adjustments made to them. For the current detail, I cannot easily identify only the records changed so I believe all records for the store/day will need to be resent.
I don't care what happens to the data in the work tables on the store side once the data has been received at HQ and processed, and the data at the HQ side will be deleted once the live tables are updated.
Would this be a good candidate for replication or would I be better off to use queries via linked servers (over a VPN) to retrieve the data?
Don Urquhart
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply