Hi All, Just wanted to check if sQL server export/import wizard takes care of referential integrity while loading data which has parent child relationships ???? I tried to check in sql server 2005 sp4 and sql server 2008 sp1. In both it gives me an error saying INSERT conflict due to foreign key constraint violation. To investigate further, i did into little further and i saved the underlying ssis package which will be created for export/import. When i checked the package, i see the data flow tasks are loaded parallely and not like loading parent tables first and then child tables next. However, i found my own work around that i loaded the parent tables first and then child tables. this worked for me. Also, the tables gets loaded absolutley fine. But sometimes it fails. Can anyone comment on this? Thanks in advance.

Myself, I stay away from the import/export wizard and copy database wizard for complex tasks with lots of objects for this reason. In fact a couple months ago another person had a similiar problem, but in this case it was some views that couldn't get created because the SSIS package created objects out of sequence. Tom Overton

Agree with Tom, SSIS Import/Export wizard should be used in case you donot need to bother about sequencing as it does not take care of such scenarios as you have seen. Having said that you could use it to setup ur package and then play around with it to save some time, though I prefer to make my packages from the scratch.My Blog | Ask Me

Thank you for suggestions.