Posted by Damien on 01/05/07 07:50

Benzine wrote:

> Hi Damien,
>
> You wouldnt by chance have a script that can update the
> status_for_replication to Not_For_Replication for all FK's?
>
> Ben
>
I'm afraid not. I believe that the first time I encountered this
problem for a project, what I ended up doing was scripting out all of
the foreign keys to a script file. Then using an editor with support
for regular expressions in find and replace (in my case, Visual
Studio), I edited the file to include the "NOT FOR REPLICATION" at the
appropriate places in the file (see Books On Line for ALTER TABLE to
find the right syntax). Then I wrote another script which just tore
down all existing foreign keys in the database. Applying these scripts
in the correct order produced the necessary changes.

On the second project, I had it included from the start, so I've never
had to do this again.

Damien

[Back to original message]