Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For sending data back and forth between tables having identical schema I have used the import/export task in management studio.

The problem is that SQLServer seems to do the import/export ops in whatever order it sees fit. This causes issues with FK constrained tables that need to be imported in the specific cascading order.

I know that I can write SSIS packages to do these ops in whatever order I like, but sometimes the import/export task is just easier for ad-hoc data changes.

Is there a way I can tell SQL Server to perform the task in the proper order for the constraints?

EDIT: I know that I can ALTER TABLE to disable and enable FK's... I guess I'm just wondering if there's a setting to make the import/export task do this automatically for constrained tables.

share|improve this question
up vote 1 down vote accepted

I don't believe there's a way to specify data transfer order to accommodate the constraints on your tables. In fact, with more than 20 tables, the wizard will "optimize" for many tables and run several table transfers in parallel.

share|improve this answer
Yeah, I didn't think so. Thanks – Matthew Aug 26 '10 at 17:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.