all groups > sql server replication > october 2007 >
You're in the

sql server replication

group:

Is there a limitation for merge replication blob?


Is there a limitation for merge replication blob? rlu
10/17/2007 9:06:49 AM
sql server replication:
hi,

Currently, I did a merge replication for BLOB. if the blob column
size less than 495MB, the synchronization is ok. if size more than
495MB, the synchronization will be failure. Does anyone has this kind
problem in merge replication?

The detail information of my merge replication are:
1. Server: windows 2003 R2 64bit, 4 CPUs and 16GB RAM
2. Microsoft SQL Server 2005 SP2 (9.0.3159) enterprise edition
3. in this test, the publication and subscriber on the same server
4. article: one artilce with varbinary(max) column
5.@stream_blob_columns='ture'
6.during test, if insert data to varbinary(max) column from file with
more than 495MB, the synchronizatin will be failure. the error message
is:

2007-10-15 18:32:03.926 The merge process could not enumerate changes
at the 'Subscriber'. When troubleshooting, restart the synchronization
with verbose history logging and specify an output file to which to
write.
2007-10-15 18:32:03.926 OLE DB Distributor 'RLU\LOCALZIMS': {call
sys.sp_MSadd_merge_history90
(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
2007-10-15 18:32:03.986 The Merge Agent was unable to update
information about the last synchronization at the Subscriber. Ensure
that the subscription exists at the Subscriber, and restart the Merge
Agent.
2007-10-15 18:32:04.166 Percent Complete: 0
2007-10-15 18:32:04.166 Category:NULL
Source: Merge Replication Provider
Number: -2147200999
Message: The merge process could not enumerate changes at the
'Subscriber'. When troubleshooting, restart the synchronization with
verbose history logging and specify an output file to which to write.
2007-10-15 18:32:04.176 Percent Complete: 0
2007-10-15 18:32:04.176 Category:SQLSERVER
Source: RLU\LOCALZIMS
Number: 0
Message: Unspecified error
2007-10-15 18:32:04.186 Percent Complete: 0
2007-10-15 18:32:04.196 Category:NULL
Source: Merge Replication Provider
Number: -2147199481
Message: The process was successfully stopped.


regards
Rlu
Re: Is there a limitation for merge replication blob? Hilary Cotter
10/17/2007 3:31:02 PM
Did you set querytimeout to a very large value - I would try 1 hour.

--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]

Re: Is there a limitation for merge replication blob? rlu
10/18/2007 8:49:51 AM
Hi Hilary,


I did set the querytimeout to 3600. it seems not the querytime
problem.

Thanks

RLU

Re: Is there a limitation for merge replication blob? Hilary Cotter
10/19/2007 8:12:23 AM
There are a couple of issues here. The first is do you have ample disk space
on the publisher and subscriber?

Secondly run profiler to see what it is doing while the sync is going on. If
you see if continually issuing calls to sp_MSenumchanges it is still
processing the changes.
400 Mgs is a lot of data to sync. Perhaps you should consider rearchitecting
this to work around this pain point.


--
RelevantNoise.com - dedicated to mining blogs for business intelligence.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
[quoted text, click to view]

AddThis Social Bookmark Button