sql server - Microsoft Sync Services - good solution for me? -

We currently upload sales transactions from our store to headoffice servers. At the moment, we use DTS (SQL Server Data Transmission Services) We are, but we will ado it. Microsoft is planning to replace Microsoft Sync services for the Net because it is Microsoft's preferred solution for this type of setup and we want to follow them standard (which is expected to be around for a long time). Here's a description of our setup and what are we planning. I am looking for some advice, especially about whether the sync service fits into our solution.

Status

Every store has a third party EPOS system that stores sales in the Microsoft Access 2000 database, which we can access. Our headoffice database is SQL Server 2005, but it will be upgraded in 2008. Headoffice is not on VPN with all the stores, but we can open our firewall in the IP address of the store so that they can send the data directly to the SQL. Server. Stores are always connected to the internet through ADSL, although they lose connections and we do not want to lose sales data. We are only uploading the transactions from the store - no need to download definitions.

Current Solution

We have written a Windows service that stores PC Download a DTS package from this service server (which includes all the details of the upload ) And runs it in the store - and it will upload the sales to our server. We have selected DTS because when you install MSDE, it is free, we can not use SSIS because every store requires a SQL Server license Shri. Another reason we chose DTS is that the details of uploads (which include tables and fields) are stored on our headoffice server, so if we need to change things we can do it at the center. There is no need to install anything new and shops. This is not a showstopper, but in our new solution it would be good for this ability.

Possible Solutions - ADO Microsoft Sync Services for Net

We currently have ADOs. Creating proof of concept with Microsoft Sync Services for Net It is an idea that SQL Server (SQL Server Compact 3.5) should be installed in each store (client) and synchronize the SQL Server 2005 database (server). We can get data in SQL CE database, either (1) it can sync with Access 2000 database or (2) EPOS system developers to write sales directly in SQL CE database - maybe (2) but our main Worrying from the store, the data is getting on the headoffice server. This method is sometimes the preferred solution for Microsoft's connected systems, and this is to say that we are serious about the sync service Appeared from. I hope that using it means that most of the work needed to upload the sale will be made in the sync service and we will not have to re-invent the wheel.

Possible Solutions - Upload to Custom Web Service

There is a possibility of uploading a sales transaction for a custom web service on our headoffice server and then In our SQL Server database this means that we have to create caching to determine which are our new lines, as well as when systems are disconnected. Apart from this, we may be missing from other functionality which will be built in sync services.

Please tell me if you have any advice that will help you, especially: "Sync service is the right solution!" The problem we are trying to solve seems very common (uploading sales from stores) - and I want to solve it with a common solution.