Not For Replication
Brian Donahue
Posts: 6,590 Bronze 1
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.
Regards,
Brian Donahue
Red Gate Techncial Support
"Tina Smith" <tb.smith@earthlink.net> wrote in message
news:6ZGIAkqCEHA.1744@server53...
> If I add the "Not For Replication" property to a column, SQLCompare
tries
> 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
to
> synchronize the table.
>
> Can SQLCompare be changed so that it uses the proper method to synchronize
> tables?
>
>
>
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.
Regards,
Brian Donahue
Red Gate Techncial Support
"Tina Smith" <tb.smith@earthlink.net> wrote in message
news:6ZGIAkqCEHA.1744@server53...
> If I add the "Not For Replication" property to a column, SQLCompare
tries
> 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
to
> synchronize the table.
>
> Can SQLCompare be changed so that it uses the proper method to synchronize
> tables?
>
>
>
This discussion has been closed.
Comments
-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.