What are the challenges you face when working across database platforms? Take the survey

Not For Replication

Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
edited December 8, 2005 4:02PM in SQL Compare Previous Versions
Hi Tina,

Thanks for your post. We are still looking into support for NOT FOR
REPLICATION columns. It's a fairly common issue that we run into.


Brian Donahue
Red Gate Techncial Support

"Tina Smith" <tb.smith@earthlink.net> wrote in message
> If I add the "Not For Replication" property to a column, SQLCompare
> to do an ALTER TABLE to do the synchronization. An ALTER TABLE can't be
> used to add this property. You really need to use the temp table method
> synchronize the table.
> Can SQLCompare be changed so that it uses the proper method to synchronize
> tables?


  • Options
    Any progress? If it's fairly common... how hard can it be :)

  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hello Nick,

    I think that if we support this, we'd support replicated database schema in general. That means extensive modifications to the scripting engine, for instance to replace all instances of ALTER TABLE DROP COLUMN to sp_dropreplcolumn.
  • Options
    While a perfect solution would be good, it might be nice to at least be able to ignore NOT FOR REPLICATION in the meantime. Presumably this wouldn't require extensive modification to the scripting engine and would help many of your customers.
This discussion has been closed.