Search code examples
sql-servert-sqlssisssis-2012ssis-2008

Best Tuning steps for SSIS packages with Execute SQL Tasks


What necessary tuning I can do in ssis level,if all of the functionality have been implemented using the Execute SQL task stored procedures. All most all tables being used are already indexed.Please suggest some useful ssis tuning tips for such kind of packages.Do I have to implement all these execute sql tasks to Data flow task!?


Solution

  • To answer your question, no. Data flow tasks, in my opinion, are mostly useful when moving data between two sources or to do complex logic that you would rather use a c# script and not use the .Net CLR in SQL Server to perform that script.

    If the source and destination are on the same instance I have never seen an occasion where SSIS data flow tasks can out-perform a properly built stored procedure.

    Because you are using execute sql tasks, there is no SSIS performance tuning. All that SSIS is doing is launching something to be done by SQL Server.

    I would focus on your stored procedures, look into the execution plans and read up on SQL Server Query Performance Tuning. It could range from a very simple index recommended when you look at the execution plan, moderate effort using Query Analyzer tool or very complex. It depends on your data and queries.