I don't really want to have FK on some reporting tables, but for obscure reasons I need to define them anyway.
I thought if I added them "nocheck" they were there but disabled.
I was able to run SSIS packages to load five interrelated tables in any order, and never got any complaints!
But just now, I did an insert of some rows on top of other rows, and got FK errors, even on my nocheck'd FKs.
So, ... "nocheck" just means not to check the existing data, but any new data *is* checked after all?
Is that right?
I guess the bulk (fast) load from SSIS manages to bypass this too?
So, there's no further way to disable the FKs, is there?
View Complete Post