December 3, 2010 at 9:33 am
We currently have replication running between multiple SQL 2008 servers and we are replicating a number of relatively large tables. We now have a need to replicate some of this data to a different server, but disk space is limited. We do not need all of the tables in this new location so is it possible to limit what tables a subscriber pulls from a publisher? I am not sure what the performance impact would be to create another publisher, but it does not seem to make much sense to have multiple publishers running when the subscriber is really what needs to be changed.
Thanks much,
Jason
December 7, 2010 at 9:33 pm
I'm curious to know what solutions people provide for this as well. We are getting more into replication, and trying to use P2P so we can go with active-active data center solutions.
At the same time, we have a reporting environment in our primary data center that needs data from only a handful of tables.
My initial thought was to create two publications, one with a subset of the reporting tables, and a second publication for the remaining tables. Create the P2P on both publications between data centers, and then create a second subscription on the reporting instance to the subset publication. One caveat to this would be if reporting needed to pull in a new table that wasn't in the subset already, but did exist in the main publication. I don't even know if that's possible, but that's the initial thought i had to prevent duplication publications of the same table.
Steve
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply