My company has a large SQL Server based app running over a local network. We are in the process of moving some staff to another building. This application needs to be available to a number of people (30) on both sides. The connection for the next few months will be very slow, ie T1.
My solution is to use SQL Server replication with three or four hour intervals. New site as publisher and distributor machine and present site as subscriber, but both sides will be making changes to the same table and possibly records. New site primarily adding new records and present site primarily updating records.
My question is this:
How do I handle the replication so that records entered on the subscription machine are not overwritten with the published data. Is this an SQL server setting or am I going to have to write an sp or something? If an SP or other method is involved a sample would be appreciated.