question about Msg 20068

Is there any work arounds to replicate a table that has more then 255
columns?
TIA,
Joe,
the most common suggestion is to partition the table and replicate it as 2
articles. Although far from ideal, this can be made transparent to the front
end by using views to amalgamate the data.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanks for the tip. I have a follow up question, if I partition the
table, will each partition need a primary key assigment?
thanks,
Joe
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uCzhYskWFHA.2664@.TK2MSFTNGP15.phx.gbl...
> Joe,
> the most common suggestion is to partition the table and replicate it as 2
> articles. Although far from ideal, this can be made transparent to the
front
> end by using views to amalgamate the data.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Joe,
this is correct, although the relationship will be 1:1. You can use a view
to amalgamate the data and an instead-of trigger to insert the data to the 2
tables.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql