blogs.conchango.com

I have raised a suggestion on Connect for a change to the current behaviour of SSIS templates. Here are the details:   Description: When you use template packages you run into problems. Mainly because all of the packages created from the same template have the same properties. The worst case being that the ID of the packages are all the ...

Someone recently left a comment on my blog about Package Template Locations asking if I could share my own template. I answered that I couldn't because I didn't have my own template that I use on all projects, across the board. It did give me an idea though; I could put together a template that exhibited as many suggestions as possible ...

For reasons that I'll save until another post, I always deploy my packages as files rather than to SQL Server. In doing this I have derived a folder structure that I use in order to keep all my deployed packages and other files in the same place:...\Root\CheckpointFiles ...\Root\Configurations ...\Root\ErrorFiles ...\Root\Logs ...

I thought it would be worth publishing a list of guidelines that I see as SSIS development best practices. These are my own opinions and are based upon my experience of using SSIS over the past 18 months. I am not saying you should take them as gospel but these are generally tried and tested methods and if nothing else should serve as a basis ...

Phillipe Cand asked me recently where you should put your SSIS templates so that you can use them as the basis for your packages. The answer is: %ProgramFiles%\Microsoft Visual Studio 8\Common7 \IDE\PrivateAssemblies\ProjectItems\DataTransformationProject\DataTransformationItems Once you have them there you can right-click on a project in BIDS ...