Following a recent forum post, I will let you find which one, I thought I would make some comments on the configurability of SSIS.
Everyone knows that a Porsche is a good car, its quick, it looks good and is generally built well. We also know that some people won't be happy with how it looks so the go down to the local auto shop and buy some bits, putting that 18inch spoiler on the back 6 inch flared wheel arches, 21 inch low profile tyres and not happy with the colour spray it pink, oh and did I mention the fluorescent tubes under the door sills. Each to their own, it’s still a Porsche.
Some people will, whilst happy with the look, aren't happy with the stereo. So pop down the auto shop again and by a new stereo and an amp or 2, some woofers, tweeters (and anything else the pet shop has) and installs the lot and can now be heard in deepest Essex from downtown LA. Each to their own, its still a Porsche.
Others whilst happy with the look and the sound of the stereo won't be comfortable with the engine. These get out there wrenches and sockets and go about replacing this bit and that until they are happy, not stopping at replacing the engine. Each to their own its still a Porsche.
Sometimes one person finds time on his hands to do all three. Each to their own its still a Porsche if only the framework shell.
So what has this got to do with SSIS, well SSIS is much like this. Almost all of the components of SSIS can be changed, you can write your own Tasks, Sources, Transforms, Destinations, Connection Managers and Log providers (all the components that make up SSIS). Whilst it might be fun to write your own and the SSIS framework has been very well designed to allow this do you really want to.
There is very little in SSIS that you can't achieve with the built in components, if you include the script task and script component then almost everything is achievable.
So strip out the standard components and write your own of everything and just use the SSIS framework, but why? Most SSIS deployments will be on a dedicated box and so you are paying for a SQL Server License (standard and above) just for a framework. In addition you have to develop and support your component(s).
I can understand that some users will need better performance in certain circumstances, but consider this; the SSIS team have spent 5 years on this, the teams quite big, are you really going to do a better job, would you just be better off with a bigger box?
You might be thinking I am against extending SSIS, well I'm not, I am really for it, but to compliment it rather than replace it. Often users tend to go down the custom route because they are not aware of what is possible out of the box (who actually reads the manual?). If you are unsure ask a question on the forums. They are lots of bods that have undoubtedly been there and done it wrong so that you don't have to.
SSIS is a flexible performance car please don't turn it into a pink boom box on wheels.