Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

SQL server 2014 - Covert existing extract SSIS package to stored procedure

$
0
0

Hello everyone,

I’m working on one of the existing Extract package.

Our customer would like to move the complete extract logic, implemented in this package to SQL stored procedure(s) as they are highly proficient in T-SQL compare the SSIS skills.

This package uses more than one Execute SQL tasks, Data Flow tasks, Pivot transformations, and Merge Join transformations.

This package extracts more than one file as result.

My concern is, is it really a good idea to move the extract logic from the Package to SQL store procedure(s)?

Will the stored procedure(s) perform well compare the current package?

Are there any performance wise differences between Pivot transformation and SQL Pivot T-SQL statement? Similarly, Merge Join transformation vs. T-SQL join statements.

Is it recommended to do such things while you already have many other SSIS package for Extract and Import work?

Please advise.

 

--

Thanks and Regards,

Ankit Shah


Thanks, <b>Ankit Shah</b> <hr> Inkey Solutions, India. <hr> Microsoft Certified Business Management Solutions Professionals <hr> http://ankit.inkeysolutions.com


Viewing all articles
Browse latest Browse all 24688

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>