July 1, 2008 at 3:48 pm
I created a new table in a data base. I then setup transactional replication. I created a snapshot and synchronized the subscriber. The new table did not go to the subscriber. Any ideas what would prevent a table from being replicated?
July 1, 2008 at 3:56 pm
Which new table? Replication is by publication, so if you create a new table, you need a new replication publication.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
May 21, 2009 at 2:30 pm
If you properly setted the replication, still table is not replicated means
* Check table has a primary key or not
* Did you added that artical in the publisher to publish
🙂
August 20, 2009 at 3:54 pm
add table to article and reinitialize. chk the log reader agent status and the snapshot agent status
August 20, 2009 at 10:24 pm
Pradyothana Shastry (5/21/2009)
If you properly setted the replication, still table is not replicated means* Check table has a primary key or noth
🙂
If there is no primary key on the table, we wont be able to put that table as an article in the publication in transactional replication.
August 20, 2009 at 10:26 pm
groads2 (7/1/2008)
I created a new table in a data base. I then setup transactional replication. I created a snapshot and synchronized the subscriber. The new table did not go to the subscriber. Any ideas what would prevent a table from being replicated?
If you have created the new table prior to creating the replication, the possibilities that it didnt get replicated is
1. you did not select that table as a part of replication
2. the snapshot agent did not run or had some issues.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply