sp_addmergepullsubscription - generates an error -- sql server replication

sql server replication : sp_addmergepullsubscription - generates an error

NS
8/21/2003 8:13:31 PM

Hi when i execute sp_addmergepullsubscription, i get the
following error.

Warning: The table 'MSsubscription_properties' has been
created but its maximum row size (8361) exceeds the
maximum number of bytes per row (8060). INSERT or UPDATE
of a row in this table will fail if the resulting row
length exceeds 8060 bytes.
Warning: The table '#olddata' has been created but its
maximum row size (9081) exceeds the maximum number of
bytes per row (8060). INSERT or UPDATE of a row in this
table will fail if the resulting row length exceeds 8060
bytes.
Warning: The table 'MSreplication_queue' has been created
but its maximum row size (9081) exceeds the maximum
number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length
exceeds 8060 bytes.

But when i reexecute the statement again, i am able to
execute it successfully.

Deepak kumar [MSFT]
8/26/2003 4:53:10 PM

Don't worry, this is just a warning message and there is nothing unusual
here.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

[quoted text, click to view]

NS
8/28/2003 10:09:49 AM

Hi Deepak.

Yes, it's a warning message only but I have noticed after
getting these warnings my desired output is not produced.
I have specified a path for the alternate folder (using
the sp_addmergepullsubscription) and when i checked the
properties the path i specified is not peresent. It
retrieved the snapshots from my the default locations.
I had to run the sp_changemergepullsubscription to change
the alternate folder.

Any comments on this matter? How do i prevent getting
these warnings?

Thanks.
NS

[quoted text, click to view]

jwirvin
10/27/2003 1:55:51 PM

Hi there. I think that the two issues are unrelated. The warning
message I believe as Deepak mentioned, is just a warning. It appears to
be happening more with SP3 from what I've gathered.

The issue with having to use sp_changemergesubscription is something
that is addressed in the following post
(http://dbforums.com/arch/69/2002/9/508754).

Basically, what I've learned from it, is if a subscription with an
alternate snapshot location is being created while connected through
something other than a direct network connection (ie: dial-up, VPN,
etc), then you have to use sp_changemergesubscription.

If, however, you have a direct network connection, then you can get
through the subscription process with no problems.

Hope this helps,

J.W.

--

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about sql server replication

View Other Months
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007

home · blog · groups

Questions? Comments? Contact the dn