Hello,
I have a requirement to maintain 3 identical tables in 3 different servers. The tables are roughly 300 rows and contain configurations for SSIS jobs.
The basic function of the table is that 1 row can only be updated by one server and then that row needs to be updated to the other two servers. Each server has it's own 'master' rows.
e.g row A updated by server1 needs to be updated to server2 and 3 (there is logic in each server so only certain rows can be updated by each server. e.g. server2 and 3 can never update row A)
My first idea was to link servers and use triggers after the table updates. this works fine, however I have concerns on the security implactions of using linked servers. Thoughts?
Is there a replication technology that would be better? Maybe transactional? My concern is that I dont want to replicate the full table to each server. Only the rows updated. And this would be a 3 way replication, each table will have 'master' rows that need to be updated on the other two servers.
Any help would be great.
Thanks