asked
Why we create SSIS packages eventhough we can accomplish the same requirement in a SP or in sql statement
What is the use of creating a SSIS package? We are calling a procedure or sql statement inside a
package.So, why don't we use a procedure directly instead of creating a package..Even in sql server agent jobs also we can use procedures instead of packages.If its because of security purpose,we can restrict it in the login level.. Somebody please answer this!!
This site runs off of voting. Please indicate helpful answers by clicking on the thumbs up next to them. If any one answer lead to a solution, indicate that by clicking on the check mark next to that answer.
SSIS Packages is not only to execute Stored procedures or script from database. There are lot of other tasks and functionality for which SSIS is. Please go through the SSIS features and functionality, you will get your answer by own.
If you are only executing a stored procedure and not using any other functionality inherent to SSIS of any kind, you're right. You shouldn't be using SSIS. SSIS has it's own overhead that's going to slow down the execution of this procedure, if the only thing going on is the execution of the procedure.
Like @vivekyadav0212 says, when you're going to use all the functionality of SSIS. It's a gigantic Extract/Transform/Load (ETL) tool for pulling data from disparate sources, modifying that data and then loading it into other disparate sources. It has tons of uses. Here's an intro from Microsoft:
http://technet.microsoft.com/en-us/library/cc917721.aspx Here is the SSIS Stairway series from SQL Server Central:
http://www.sqlservercentral.com/stairway/72494/ Those will give you some idea of all the functionality. But just running a stored procedure and absolutely nothing else... No.
16 People are following this question.
