Pull subscription

Question

Post reply

Pull subscription

bill-719006

SSC Journeyman

Points: 89
More actions
March 6, 2009 at 4:39 am

#201037

Hello -
We recently set up a pull subscription between two SQL Servers 2005 databases.
We have seen the sp_MSUpd_tblMain stored procedure has twice as manay parameters as we would expect.
Also, the SQL that CALLS the sproc specifies the expected number which generates a SQL error and the replication does not complete.
Can anyone explain this?

Viewing 6 posts - 1 through 5 (of 5 total)

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

ab5sr SSCarpal Tunnel Points: 4056 More actions · Answer 1

What service pack are you using on these servers?

bill-719006 SSC Journeyman Points: 89 More actions · Answer 2

Hi Lee -

thanks very much for your reply.

It turns out that both ar SQL Server 2000, SP4 (not 2005 as described.)

Does this help?

Bill

noeld SSC Guru Points: 96590 More actions · Answer 3

SQL 2005 by default uses SCALLs for updates.

SQL 2000 by default uses XCALLs for updates.

* Noel

bill-719006 SSC Journeyman Points: 89 More actions · Answer 4

That was it! The publisher was set to MCALL while the subscriber was expecting XCALL. Thanks for that.

This replication was being re-established after the Publisher was rebuilt.

I assume if we had completely deleted the tables on the subscriber and re-created the subscription from scratch that would have synced them up correctly?

Bill

noeld SSC Guru Points: 96590 More actions · Answer 5

bill (3/6/2009)
That was it! The publisher was set to MCALL while the subscriber was expecting XCALL. Thanks for that.
This replication was being re-established after the Publisher was rebuilt.
I assume if we had completely deleted the tables on the subscriber and re-created the subscription from scratch that would have synced them up correctly?
Bill

No clue why it did not recreated the procs correctly then.

* Noel