Replication 255 column limit

Is there a workaround for this limitation? I.E can I just use the
column filters option when setting replication up to get around this?
You could upgrade, for a out-of-the box support. Otherwise what people tend
to do is partition the table and replicate the partitions, related by a
PK-PK join. You could present the tables as the original one to the users by
using a view and an instead-of trigger.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Rob,
It may also be possible to publish an indexed view containing a subset of
the columns as a logbased article (replicate indexed view as table...) if
you can take the performance hit of having the indexed view hanging around
at the publisher.
-Raymond
<robert@.orisoft.co.uk> wrote in message
news:1161004229.423453.155350@.i42g2000cwa.googlegr oups.com...
> Is there a workaround for this limitation? I.E can I just use the
> column filters option when setting replication up to get around this?
>
|||Sorry - just read Raymond's answer and realised I had misinterpreted the
question. To replicate a subset of the table you could use indexed views or
vertically partition the table in the publication wizard. I'll test this,
but as far as I recall the colid is used to determine the max article size,
and as this might still be > 255 the issues may well remain.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||When you are creating a merge/transactional publication, the wizard
(through advanced options) allows you to specify column filters, if I
only tick upto 255 will that get round it? Its for reporting so we dont
need all the data anyway.
Rob
Paul Ibison wrote:
> Sorry - just read Raymond's answer and realised I had misinterpreted the
> question. To replicate a subset of the table you could use indexed views or
> vertically partition the table in the publication wizard. I'll test this,
> but as far as I recall the colid is used to determine the max article size,
> and as this might still be > 255 the issues may well remain.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||As far as I recall, this will work only if you haven't already deleted some
columns in the table before the 255 you select, assuming these are the
initial 255 columns in the table ie the colid must always be below 255. I'll
verify this but have a big workload at the moment.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .