We have a main OLTP database and are setting up transaction replication for a reporting database.
We have say 1,000 tables.
Maybe 500 of them clearly need to be replicated in near-real time.
Another 100 are transaction related and do NOT need to be replicated at all, do not really need to be present on the reporting side but are harmless if old copies are there.
Another 200 need to be present on both sides, but will be written on both sides so should NOT be replicated - do not need to communicate changes either way.
The remaining tables might be needed sometimes on the destination side, but maybe it's just as easy not to fix up their PKs and not to publish them, but just as a best practice (??) resync the two sides once a month or so with a full backup, let us assume they would be read-only on the reporting side.
The total database size is a modest 20gb or so.
Does that make sense? Or should I bite the bullet and replicate the last 200 or so just in case?
Thanks,
Josh