tc3596
Technical User
- Mar 16, 2001
- 283
Here is my situation. I have a table which has 1 column. This column contains the table names I need scripted out to their own individual sql files. Via a SSIS package, I loop through each row and create a table script with dependencies set to true. That all works great.
Here is my dilemna. If the withdependencies option is set to true, it scripts out the table "tblCodes" along with a create script for "tblCodesTypes" in the same script...Perfect, this is what I want.
However, when the loop comes back through again, it wants to create another script for "tblCodesTypes"...this is bad. How do I avoid this? The table script name in this scenario would be "tblCodes.sql" which would contain create scripts for both tables.
Here is my dilemna. If the withdependencies option is set to true, it scripts out the table "tblCodes" along with a create script for "tblCodesTypes" in the same script...Perfect, this is what I want.
However, when the loop comes back through again, it wants to create another script for "tblCodesTypes"...this is bad. How do I avoid this? The table script name in this scenario would be "tblCodes.sql" which would contain create scripts for both tables.