SSIS Design Patterns : Converting all T-SQL Task to SSIS components [closed]

StackOverflow https://stackoverflow.com/questions/22171671

Question

There is A SUGGESTION to redesign all the SSIS package in a project.The thing is ,at the moment all functionality has been implemented using the T-SQL stored procedures(Execute SQL Task).I have been asked to redesign all those T-sql tasks to ssis components.

When I checked the stored procedures,these are not complex t-sql and it has to handles only small data sets.

I can not see any benefit of implementing all these using the SSIS Components.Please share your thoughts and experience / any other sugestions ,if you are an SSIS developer

Was it helpful?

Solution

Standardization.

SSIS in general has a hugh disadvantage towards tsql - it pulls the data out (unless you just send SQL to the database. It's main advantage is a lot more flexibility and actual power than SQL (plus it can run on another machine, adding scalability).

In your case it seems somoene has decided to standardize on SSIS packages, likely for standarizing - and this makes a certain amount of sense. Not saying in this case, just that standardization is a good thing in general. The rest is opinion based - so I will not talk about it here.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top