February 8, 2009 at 2:57 pm
Hi folks,
Someone may be able to help me here.
I have an overnight job that needs to drop the pull transactional subscription on our db. Run an identical job on both servers to "cleanse" millions of records. Then add the subscription back in.
1) Generating scripts left me with settings that do not actually exist like Continuous replication and auto sync. I took these out - why goes generating a script not provide you with your actual settings?!?!
2) MORE IMPORTANT - When the subscription is added back, it is trying to deliver (and failing on the primary key) thousands of transactions from the last few days. Why so? What causes this behaviour? This will be a massive problem for an automated process.
Thanks for any help!
February 8, 2009 at 3:02 pm
Actually I think it may be trying to resync everything. DO NOT NEED it doing that. I thought I'd turned sync off in the script, am I missing something?
use [LIVEDB]
GO
exec sp_addpullsubscription @publisher = N'LIVE2', @publisher_db = N'LIVEDB', @publication = N'LIVEDB-Proposals', @independent_agent = N'true', @subscription_type = N'pull', @description = N'Transactional publication of LIVEDB database from Publisher LIVE2.', @update_mode = N'read only', @immediate_sync = 0
exec sp_addpullsubscription_agent @publisher = N'LIVE2', @publisher_db = N'LIVEDB', @publication = N'LIVEDB-Data', @distributor = N'LIVE2', @subscriber_security_mode = 1, @distributor_security_mode = 0, @distributor_login = N'', @distributor_password = N'', @frequency_type = 4, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 4, @frequency_subday_interval = 10, @active_start_date = 0, @active_end_date = 0, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @enabled_for_syncmgr = N'false', @use_ftp = N'false', @publication_type = 0, @dts_package_location = N'subscriber', @offloadagent = N'false'
GO
Is the distributor set wrong maybe? Should be the pull subscriber?
February 8, 2009 at 3:47 pm
Just FYI I solved this. I did not script the Distributor side just the subscriber side, hence the problems. All ok now.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply