Same database, Multiple Publications in SQL Server 2005 Replication
June 1, 2010 12:46 PM Subscribe
How can I have multiple publications in SQL 2005 using the same source database?
Scenario as follows:
Main database is called MainDatabase. I have an existing transactional publication set up on MainDatabase. This is working fine. It replicates to a database called ReportingDatabase.
I want to set up another publication from MainDatabase, and have it only replicate a subset of the data (4 tables) to a separate subscriber, called SeparateDatabase.
When I set up the second publication, I select the 4 articles to publish, generate the snapshot, and all is well. However, when I set up the second subscription, select the publication, it finishes, but the snapshot is never delivered. The status is stuck on this message:
The concurrent snapshot for publication 'SeparateDatabase' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publicati
And yes, the error message is truncated by SQL 2005, not by me.
I have a feeling I'm leaving some pertinent info out here, so please let me know if other information would help in troubleshooting.
The distributor is set up on the same server as MainDatabase, and the distribution database is called 'distribution'.
Thanks in advance.
Scenario as follows:
Main database is called MainDatabase. I have an existing transactional publication set up on MainDatabase. This is working fine. It replicates to a database called ReportingDatabase.
I want to set up another publication from MainDatabase, and have it only replicate a subset of the data (4 tables) to a separate subscriber, called SeparateDatabase.
When I set up the second publication, I select the 4 articles to publish, generate the snapshot, and all is well. However, when I set up the second subscription, select the publication, it finishes, but the snapshot is never delivered. The status is stuck on this message:
The concurrent snapshot for publication 'SeparateDatabase' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publicati
And yes, the error message is truncated by SQL 2005, not by me.
I have a feeling I'm leaving some pertinent info out here, so please let me know if other information would help in troubleshooting.
The distributor is set up on the same server as MainDatabase, and the distribution database is called 'distribution'.
Thanks in advance.
This thread is closed to new comments.
posted by jbiz at 1:50 PM on June 1, 2010