December 6, 2013 at 10:02 am
Comments posted to this topic are about the item You'd like to load lots of historical data...
March 15, 2016 at 7:00 am
We had to do this when we were migrating data to our new system.
March 15, 2016 at 7:42 am
.. 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?
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 15, 2016 at 11:28 pm
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. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply