Post reply

Transaction replication and editing a subscriber

  • March 10, 2005 at 10:03 am

    #87806

    Hi,

    I have a problem that I hope someone might be able to shed some light on.  I have Transactional Replication (with Immediate and queued updating) setup in SQL 2000 with a single table replicated.  The table has 135 columns and when I try to update any column on the subscriber it fails with this error.

    'Another User has modified the contents of this table or view; the database row you are modifying no longer exists in the database.  Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server]Must declare the variable '@bitmap'.'

    Rows can be inserted and deleted on the Publisher and subscriber ok, its only when a column is updated on the subscriber that it fails.  I have this setup on two different locations and get the same error on both.

    If I remove one of the columns then it works ok but the limitation is meant to be 255 columns on replication so I'm a little confused.  I've re-created the publication many, many times with no effect.

    As an experiment I added more columns and I get a different error for each columns added.  An example is below

    [Micorsoft][ODBC SQL SERVER Driver][SQL Server]Incorrect syntax near the keyword 'declare'.  [Microsoft][ODBC SQL SERVER driver][SQL Server]Must declare the variable '@c130o'.'

    The @variable name changes for each column added

    I think its something to do with the update trigger but need a few pointers on correcting it.

     

    Any ideas?

    Thanks

  • March 11, 2005 at 2:09 pm

    #546737

    It seems a problem with the stored procedures used to replicate. Run sp_HelpArticle to see the names of the stored procedures. Check the update_command column and edit that stored procedure at the subscriber. Try to find any error in the columns declared at first or the bitmap values.

    It will depend of the configuration but if you run sp_scriptpublicationcustomprocs, the sp, might return the sintax needed to create the correct stored procedures. Copy the output and run it at the subscriber to reset the stored procedures.

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply