>Hi,
>I have POS application that running in multiple branches and also HQ. I need to transfer all the sales records from branches back to HQ; update products' info such as cost or new product to branches.
>
>I would like to know, what are the options available to achieve this? What is the cost?
>
>Thank you

See merge replication in BOL:

Merge replication allows various sites to work autonomously (online or offline) and merge data modifications made at multiple sites into a single, uniform result at a later time. The initial snapshot is applied to Subscribers and then SQL Server 2000 tracks changes to published data at the Publisher and at the Subscribers. The data is synchronized between servers either at a scheduled time or on demand. Updates are made independently (no commit protocol) at more than one server, so the same data may have been updated by the Publisher or by more than one Subscriber. Therefore, conflicts can occur when data modifications are merged.

Merge replication includes default and custom choices for conflict resolution that you can define when you configure a merge publication. When a conflict occurs, a resolver is invoked by the Merge Agent to determine which data will be accepted and propagated to other sites.

Options available with merge replication include filtering published data horizontally and vertically, including join filters and dynamic filters, using alternate synchronization partners, optimizing synchronization to improve merge performance, validating replicated data to ensure synchronization, and using attachable subscription databases.

Merge replication is helpful when:

Multiple Subscribers need to update data at various times and propagate those changes to the Publisher and to other Subscribers.


Subscribers need to receive data, make changes offline, and synchronize changes later with the Publisher and other Subscribers.


The application latency requirement is either high or low.


Site autonomy is critical.