I know there's a limitation of 256 columns to the tables I can publish via replication, however I would like your help in solving my issue.
I need to provide for a replication between the main office application, and the website, sitting at different phsyical locations. Both locations have to update, among others, the "main" table which has over 256 columns. Why and how this table reached these columns is out of scope of this discussion, I know it's bad :)
Since it's only one table which is the problem - the rest (around 20) are much smaller - I'm trying to think of a creative solution.
The replication needs to be merge replication, since they have to be able to update from both locations, and the changes should be immediately visible on the other side. Both servers are SQL Server 2008, connected via a VPN.
Any ideas for a workaround? Also - if I just choose 256 columns to replicate (I don't need all columns on the website) - will this work well? Can I keep the other columns on the website, but just not replicate them?