Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 Trf Initial Snapshot Manually

Author  Topic 

Ken Blum
Constraint Violating Yak Guru

383 Posts

Posted - 2008-09-07 : 17:11:08
I have a subscription which uses web synchronization, and that is the only way the system can connect to the publisher. The initial snapshot is 500+MB, so it's failing to initialize. I've tried increasing the timeout with no luck. I know that both databases are the same since the published database came from the subscriber server, I setup the publication, and then restored the database to the subscription database.

1. Is there any way that I can tell replication to ignore the snapshot & just start replicatiing?

2. If I can't do #1, then I would like to deliver the snapshot manually (via a zip file) and then extract it on the subscriber server. How can I tell it to use the local folder for the snapshot initialization?

TIA,

KTB

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2008-09-07 : 17:13:42
1. Yes, just don't create the snapshot during setting up the publication and then uncheck the "initialize" box when setting up the subscription. You could finish it off by disabling the snapshot job, but that job is pretty much pointless after you've setup replication.


Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

Ken Blum
Constraint Violating Yak Guru

383 Posts

Posted - 2008-09-07 : 18:57:25
Thanks Tara - Since I am using Web synchronization and direct connection is not an option, I have to create the subscriptions using T-SQL. I just found the "@sync_type" option which if set to "none" will supposedly not download the data files. Note that this is a pull merge subscription, and it does say that "No-synch subscriptions are not supported for merge pull subscriptions." according to KB 320499. I hoped that statement was wrong, So I restored my published DB to the subscriber server, and then setup the subscription like so...

I did this on the subscriber machine (in Texas):


use [WorkTrack]

exec sp_dropmergepullsubscription @publisher = N'GWDDBRDEV001',
@publication = N'SDP_GK_Coppell',
@publisher_db = N'SDP_GK_Coppell'


exec sp_addmergepullsubscription @publisher = N'GWDDBRDEV001',
@publication = N'SDP_GK_Coppell',
@publisher_db = N'SDP_GK_Coppell',
@subscriber_type = N'Local',
@subscription_priority = 0,
@description = N'',
@sync_type = N'none'

exec sp_addmergepullsubscription_agent @publisher = N'GWDDBRDEV001',
@publisher_db = N'SDP_GK_Coppell',
@publication = N'SDP_GK_Coppell',
@distributor = N'GWDDBRDEV001',
@distributor_security_mode = 0,
@distributor_login = N'GK_Coppell',
@distributor_password = N'spindle',
@enabled_for_syncmgr = N'False',
@frequency_type = 1,
@frequency_interval = 0,
@frequency_relative_interval = 0,
@frequency_recurrence_factor = 0,
@frequency_subday = 0,
@frequency_subday_interval = 0,
@active_start_time_of_day = 0,
@active_end_time_of_day = 235959,
@active_start_date = 0,
@active_end_date = 0,
@alt_snapshot_folder = N'',
@working_directory = N'',
@use_ftp = N'False',
@job_login = null,
@job_password = null,
@publisher_security_mode = 0,
@publisher_login = N'GK_Coppell',
@publisher_password = N'',
@use_interactive_resolver = N'False',
@dynamic_snapshot_location = N'',
@use_web_sync = 1,
@internet_url = N'https://SpindleServices.com/SDP_Replication',
@internet_login = N'SDP_User',
@internet_password = N'',
@internet_security_mode = 0,
@internet_timeout = 1200


And then this on the publisher (here in Chicago):

use [SDP_GK_Coppell]
exec sp_addmergesubscription @publication = N'SDP_GK_Coppell',
@subscriber = N'DG79FXF1\GK_COPPELL',
@subscriber_db = N'WorkTrack',
@subscription_type = N'pull',
@subscriber_type = N'local',
@subscription_priority = 0,
@sync_type = N'none'


I then did a Synchronization on the subscriber and it STILL is downloading the bcp's. It also wiped out my rowguid columns from the db restore. sheesh!

I will try it without creating a snapshot like you say. If that doesn't work I see where there is an @alt_snapshot_folder in the agent SPROC so I will trf the snapshot manually to the subscriber server and then try that.

From now on no machine will leave Chicago before replication is already setup!

Any other ideas let me know

Thanks,
Ken
Go to Top of Page

Ken Blum
Constraint Violating Yak Guru

383 Posts

Posted - 2008-09-07 : 21:57:02
After 2 days of trying this & that, I finally figured out how to use an Alternate Snapshot Folder with Compression, which made a usable 35MB snapshot instead of 500+MB.

Thanks Tara.
Go to Top of Page
   

- Advertisement -