Hi I use SQL tasks in my ssis packages. The problem is I have some scripts that are 2000 lines of SQL code long. So when you just copy teh SQL script into the editor of the sql taks it my cut the half of your script and you never notice. Did you experience this already? So I decided not to copy the SQL code directly into the task editor but use a file connection to the SQL script. The result is fine but everything slowed down in Visual studio. Does ist come from my changing to file connections to huge SQL scripts...? Do you know a way to improve the situation? Thanks!!! SergioGreetings from No Planet!

Use a stored procedure instead: solves both problems.Arthur My Blog