Eric M Russell (3/15/2016)
.. You wish to temporarily disable all foreign key constraints on the table since this is an archive database and you orphaned records are acceptable for this one load only ..
The question was asking how to temporarily disable the constraints, but the real question is:
Why you would even want to keep foreign key constraints on a historical archive table that you know will contain orphan rows?
<headdesk> You beat me to it again except that I'll ask why would anyone even think of adding FKs to a history table? Ostensibly, the source table has FKs that already checked the data and those FKs could change over time. History tables need to accurately record what happened and when. There should never be FKs on history/audit tables.
It did, however, make for an interesting question. :-D
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Helpful Links:
How to post code problemsHow to post performance problemsForum FAQs