I took the following from BOL...
Replication->Planning for Replication->Evaluating the Replication Env->
Planning for Application Development
"A table used in a merge publication can have a maximum of 246 columns and a
maximum row size of 6,000 bytes"
Is this true? Whats the actual impact on the system when a row size exceeds
6,000 bytes? I have a merge replication setup that has text and image columns
that well exceed the limit stated above, but I have not encountered any
issues. Are the sizes of text and image data columns counted in Microsofts
reference to "maximum row size" -or- do they just count the size of a pointer
in a text column (16 bytes)?
Does this only become a problem when databases are large? My test db is
about 800MB.
I calculated the row size in my db by running select data_length(column_a)
from table_a
Thanks,
Alex C.
my experieince is that only the first 6000 bytes will be logged to the
conflict tables. Note than you can replicate more than 6k using merge, but
if you have any conflict the conflict tables will only record the first 6k
bytes of the conflict.
"acastner" <acastner@.discussions.microsoft.com> wrote in message
news:E5D069BB-74E4-471C-A342-14542F8C8FAE@.microsoft.com...
> I took the following from BOL...
> Replication->Planning for Replication->Evaluating the Replication Env->
> Planning for Application Development
> "A table used in a merge publication can have a maximum of 246 columns and
a
> maximum row size of 6,000 bytes"
> Is this true? Whats the actual impact on the system when a row size
exceeds
> 6,000 bytes? I have a merge replication setup that has text and image
columns
> that well exceed the limit stated above, but I have not encountered any
> issues. Are the sizes of text and image data columns counted in Microsofts
> reference to "maximum row size" -or- do they just count the size of a
pointer
> in a text column (16 bytes)?
> Does this only become a problem when databases are large? My test db is
> about 800MB.
> I calculated the row size in my db by running select data_length(column_a)
> from table_a
> Thanks,
> Alex C.
Friday, March 23, 2012
Merge replication row size question...
Labels:
application,
bol,
database,
env-gtplanning,
following,
merge,
microsoft,
mysql,
oracle,
replication,
replication-gtevaluating,
replication-gtplanning,
row,
server,
size,
sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment