Snapshot agent

Question

Snapshot agent

shanila_minnu

Hall of Fame

Points: 3465
More actions
November 24, 2009 at 8:36 am

#156433

i am trying to setup a transactional replication.I created one database in publisher with some data and the same database with same data in subscriber.In this case ,should i need to run the snapshot agent . In production the databases are too big

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Bru Medishetty SSC-Insane Points: 23606 More actions · Answer 1

shanila_minnu (11/24/2009)
i am trying to setup a transactional replication.I created one database in publisher with some data and the same database with same data in subscriber.In this case ,should i need to run the snapshot agent . In production the databases are too big

Sorry to make this reply a very short one..

I actually did reply to the same post and when submitted, could not submit and lost everything I typed.. 😉

Any way, here is my questions to understand what you did.

You mentioned you created on DB in publisher with some data and towards the end say the production db's are too big, are you now setting a test system, with some data ?

And what do you mean by created same database with same data in subscriber ? You already ran a backup copy of the publisher on subscriber?

A snapshot agent is responsible to create the initial snapshot of the articles involved in transactional replication. You need to run it for initially.

I don't know if I could follow your question completely so these are the questions I have to know better.

Bru Medishetty

Blog -- LearnSQLWithBru

Join on Facebook Page Facebook.comLearnSQLWithBru

Twitter -- BruMedishetty

homebrew01 SSC Guru Points: 55553 More actions · Answer 2

I think you can avoid a snapshot if you have created the subscriber by another method. But you have a risk of data getting out of sync if you do not capture all the publisher transactions since the subscriber was established.

When you create the publication, I think you have options about creating a snapshot or not if the subscription already exists.

You could set up a small practice database to test the options.

happycat59 One Orange Chip Points: 29451 More actions · Answer 3

Transactional replication is quite happy to have a subscriber that already has the data - hence avoiding the need to use a snapshot. If you choose this option, you are responsible for ensuring that the subscriber actually has all the table and data. The simplest way to do this is to use a database backup. Books online has details on how to do this.