SQL Server Performance

limit 255 columns in table publishing?

Discussion in 'Performance Tuning for SQL Server Replication' started by SHU, Feb 19, 2005.

  1. SHU New Member

    Can I bypass restriction in 255 columns at creation of the publisher?
    I use transactional replication.
  2. satya Moderator

  3. chriscec New Member

    Yeah, I've got the same problem with a table with more than 255 columns. I use SQL Server 2000 SP3.
    Any ideas of how to bypass this limit? Or if it's not possible, any replication alternative? (Log shipping is not an option in my case, as the secondary database must be online all the time for user's connections)

    Thanks in advance.
    Chris
  4. satya Moderator

    Even though the limit of no.of columns in SQL 2K is 1024, the limit of 255 columns in replication is not changed. So unfortunately it is not possible and books online refers A table used in a snapshot or transactional publication can have a maximum of 255 columns and a maximum row size of 8,000 bytes." This is under the article "Publishing Data and Database Objects".

    Its better to breakup the table and preserve existing select functionality to create a view and you may need to re-write the insert/delete procedures.

    HTH

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.

Share This Page