Snapshot alters my forgien keys.
David Roussel
'delete the existing data that matched the row filter', I've also tried the
truncate option too. However what I don't want is to delete the tables and
add them again. The reason I didn't want to do this is that I have other
tables that foreign key to the replicated data. So if the tables were
dropped I'd lose all my existing relationships.
What I have found is that even if I choose not to drop the tables, the
snapshot removes all foreign key anyway!
In the snapshot.pre file the stored proc sp_MSdroparticleconstraints is run
against each table. This stored proc drops all constraints (unique
constraint, primary key, foreign keys, check constraints) from the tables.
I had realised earilier that something funy was going on with my foreign
keys and wrote a pair of scripts to run before and after the snapshot to
drop and then add again, all foreign keys to the subscription tables. Now
I've goint to have to modifiy it for all constaints too.
Why does SQL Server do this? Surely BCP can insert if there is a constaint?
Is there any way to turn this behaviour off?
Thanks
Dave
Raj Gill
David Roussel
it for reasons I can't remember (like getting my script that addes the FKs
back to work).
So if I don't set this option sp_MSdroparticleconstraints will not be
called?
If I uncheck the option in the GUI, then the 'Nonclustered indexes' option
can't be unchecked. If I'm supplying my own indexes before applying the
snapshot, then I'd like none of these options. Can I just pass 0 as the
schema_option parameter to sp_addarticle?
Thanks for the hint.
Dave
"Raj Gill" <gillra...@hotmail.com> wrote in message
news:u0Wo3ZGSCHA.1792@tkmsftngp13...
