SQL Replication: Which tables/views should be a part of replication?
I have replicated entire databases, performance is an issue with frequently changed data when your talking larger volumes. For us, a larger amount of data was 500gb of data being supported by 32gb of memory and 8 cores (didn't have control or say in hardware specs). We had transactional replication, and about 1-2 times a month it would get behind, far enough behind where we had to re-snapshot it to get our subscriber current (this would take us about 4 hours each time). Whenever replication had an issue and data started to queue up, it just couldn't catch up.