Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Replication not workiing


Replication not workiing

Author
Message
MarvinTheAndriod
MarvinTheAndriod
SSC Veteran
SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)SSC Veteran (298 reputation)

Group: General Forum Members
Points: 298 Visits: 1291
Lempster (1/30/2014)
MarvinTheAndriod (1/30/2014)
The Publication that say "The initial snapshot for publication is not yet available." is the one that isn't working.

Should I reintialise again. Is it worth starting the snapshot agent ?


Yes! If the snapshot agent is not running then the snapshot will not be created. The subscription may be marked for reinitialisation, but nothing will happen until the snapshot agent runs. Do you have the snapshot agent set to run on a schedule - once per day for example?

Regards
Lempster


I don't beleive so, as the Replication monitor says the Snapshot agent last start time was over a year ago, and according to the view syrchonsation status it is not running now, but my knowledge of replication is very limited. Would there be a job for it if it was scedhuled once a day ?
Lempster
Lempster
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2683 Visits: 1657
Yes, there would be a SQL Agent job for it. You only need to generate a new snapshot if you need to reinitialise a subscription, e.g. because a new article has been added to a publication, or because of a replication error - they can be difficult to troubleshoot and so sometimes the 'sledgehammer' approach is to generate a new snapshot (via reinitialising a subscription). Of course, if your publication is huge, it's going to take a long time to generate the snapshot and push it to the distributor and the subscriber so you may want to be a little more surgical in that case.

There's no harm in scheduling a snapshot agent to run every day because it won't do anything other start up and shut down if it determines that no subscriptions need to be reinitialised.

It might be worth your while grabbing a book on SQL Server replication or at least look it up in BOL or find resources on the web.

Regards
Lempster

EDIT: spelling mistakes
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search