Hi Paul,

Thanks for the reply.

Will definitely try the drop and re-apply approach. Up until recently our time has been very limited with our overnight jobs but that could change soon.

The...

Hello David,

Are your article defaults set to DROP and recreate the table at the subscriber?

And your servers are on the same network and one server can be registered with the...

I take it this is Transactional replication ??

Is this error in the Distribution agent ?

Graeme

Hi,

I'd have to agree with previous replies. Your query is far to broad, you are selecting all columns and all rows. That means the only factor that is likely to...

Hi,

Need a bit more information on the process you went through to set up your replication. 

Did you synchronise before adding the subscriber or did you push out a new...

Hi,

The databases were rebuilt yesterday and the jobs have been re-run. It looks like the procedure is now running normally ????....seems very odd.

I'll keep an eye on that.

Thanks for your...

Yeah, the data is almost the same, the jobs run the same time on each server and the processes are virtually the same. The server with sp4 is a lower...

Hi,

I use this

DECLARE @DBName VarChar (255), @Cmd VarChar (500)

DECLARE DBCursor CURSOR

FOR

SELECT [name] FROM sysdatabases WHERE [name] IN ('List','Your','databases')

OPEN DBCursor

FETCH NEXT FROM DBCursor INTO @DBName

WHILE @@FETCH_STATUS = 0

BEGIN

  SET @Cmd =...

It sounds like you are dealing with people who don't understand how replication works. My advice would be to have a look at some simple replication articles/books/BOL so that you...

What you have here purpose are two ways of the doing the same thing. The replication solution allows you to distribute the data to multiple sites in a quick and...

Hi Bill,

If you are using snapshot replication that is the easiest to deal with. All you will be doing is taking a copy of the data and placing it on...

I think you may have to re-apply replication to this restored database...re-subscribe or re-publish.

The logreader is probably referring to the pre-restored version.

Reapplying the rep will set up a new logreader

HTH

Graeme

You should only use the data and schema exists option if the data is already synch'd at both ends..if you make a change to a record at one end it...

Have you tried unregistering and re-registering the re-named server on server A.

You might have to drop the subscription and re-subscribe to server A

Regards...Graeme

Hi Jennifer,

Having read the posts, it looks like Merge Replication is the right solution for you. Each server will have it's own ranges of IDs so there shouldn't be any...