November 21, 2003 at 3:07 am
can someone else share my problem.
I've created a publication for transactional replication type.And has been set it to
immediate updating and queue updating.
Base on this publication, i created a push subscription with "Immediate Updating with Queued Updating as a Failover".
After the subscription created (from publisher), i went to the subscriptions (subscrber)and set the update method to Queued Updating as a Failover.
When i insert a new record at subscriber's database, the new record will be inserted into the publisher database table as well.
MY PROBLEM
But, after i try to insert more than 2,3 or 4 thousand record, updating is not working anymore.
i've observed relevent agent used, when i insert one new record from subscriber database, the Log Reader Agent is running then the distribution Agent.
*Sometime the Queue Reader Agents is running too.
i know that, as long as the subscriber's MSreplication_queue table having data then this agent is read the data from there
Actually, what is the sequence for these agent running (transactional replication)
Thank you
November 24, 2003 at 12:00 pm
This was removed by the editor as SPAM
November 25, 2003 at 4:52 am
What Hapans When you reinitilzes the subscription
December 6, 2003 at 12:25 am
Thanks for your reply Gil_Adi.
I've tried to reinitialize the subscription, but nothing changed. Only the snapshot is run again, when updating the data from subscriber the publisher no any update
Thanks
December 6, 2003 at 7:02 am
I'd recommend turning the logging on for all agents via a switch in the job. I've used queued updates with no issues at all. Not clear from your post, the changes from pub to subscriber are failing, or from subscriber to pub?
Andy
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply