Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to keep several tables in two different databases mirrored. Both databases are within the same server, and both are SQL Server dbs. This mirroring only affects the data they contain, not the structure (although would be great if any table alteration was reflected as well). The data volume in those tables is low and only changes from time to time. There will be other tables in both databases that should't be mirrored. The following list contains all the options I think I have:

  • Use triggers. Perhaps the best option, but as I want to mirror lots of tables this might imply more work.
  • Implemente SQL Server replication. I did this in the past on another pair of dbs and was really difficult to set up and wasn't working as desired, in terms of performance. This time the conditions are completely different, so it might work.

Does anybody know if there are other options? Which one do you prefer and why?


share|improve this question
DDL triggers With a bit of modification, this works fine Link – user55547 Dec 23 '14 at 9:14
Replication seems to be your best option here. Why was it slower than expected when you tried it? Which flavour of replication? Merge? Transactional? Are both copies writeable or is there a read-only copy of the tables? – spaghettidba Dec 23 '14 at 9:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.