Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

snapshot publication - time out expired Expand / Collapse
Author
Message
Posted Thursday, November 6, 2008 5:24 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Tuesday, December 16, 2014 8:55 PM
Points: 1,076, Visits: 3,054
Hi Friends,

I configured merge replication in one the sql server 2000. when completion publication after that automatically snapshot agent is running and creating article, while running snapshot agent it is automatically turned off (time out expired), so article was not created. Becuse all tables contain 20Laks recored. still snapshot publication not yet available.

After that... I creted new replication agent profile, and create new parameter & value as follows

-BcpBatch size 100000
-History Verbel - 2
-Logintime out - 15
-MaxBcpThreads -1
-Query time out - 1000

It was taking too long time for creating snapshot publication .

Anybody give me tips, how to reduce the time for creating snapshot publication .

Thanks
Post #598024
Posted Friday, November 7, 2008 5:55 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, October 27, 2014 7:59 AM
Points: 177, Visits: 757
Hi Ananda,

Make sure your snapshot goes onto a fast disk because it is mainly IO intensive. You can increase the -MaxBCPThreads to a number equal to the number of processors on your machine.

If your tables doesn't have uniqifiers, you might want to add them yourself before you generate the snapshot rather than them being created during Snapshot (see http://msdn.microsoft.com/en-us/library/aa237151(SQL.80).aspx, "Improving Performance While Generating and Applying Snapshots" for details).

Having said this, it is odd that you get a time out because the job is diveded into many steps. Is there anything in the Snapshot history that reveals where it is timing out? Next time you attempt, increase the HistoryVerboseLevel to 3.

HTH!

/Elisabeth


elisabeth@sqlserverland.com
MCITP | MCT
http://sqlblog.com/blogs/elisabeth_redei/
http://linkedin.com/in/elisabethredei
Post #598836
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse