OK last time I touched SQL replication was some time ago and I could do with some advise on alternatives. I'll keep it nice and simple.
One server. One client. Some tables in a db need replicating between the two, in specific directions.
Server runs SQL 2012 Standard. Client 2012 Express.
Some tables need Server > Client only.
Some tables need Client > Server only.
One table needs bidirectional.
Simple.
Client will be d/c at times so I would be looking to merge replication and pull subscriptions and then to manage the directions per table. Will give me control on conflict resolution also if required. Obviously for this to work in Express I would require a synchronization task/process in additional to SQL.
So my question is, is replication still the way to go for these sort of requirements? What are my alternatives? Licensing is fixed, so express must stay etc.
Thanks in advance for any advice.
One server. One client. Some tables in a db need replicating between the two, in specific directions.
Server runs SQL 2012 Standard. Client 2012 Express.
Some tables need Server > Client only.
Some tables need Client > Server only.
One table needs bidirectional.
Simple.
Client will be d/c at times so I would be looking to merge replication and pull subscriptions and then to manage the directions per table. Will give me control on conflict resolution also if required. Obviously for this to work in Express I would require a synchronization task/process in additional to SQL.
So my question is, is replication still the way to go for these sort of requirements? What are my alternatives? Licensing is fixed, so express must stay etc.
Thanks in advance for any advice.