SSIS: Export mappings for documentation, etc
Hi, I have SSIS packages with the usual: source, destination, and mappings between the two. How can I export these mappings to, say, Excel / Word for documentation purposes? Thanks.
March 1st, 2008 10:44am

Hi, There are a number of ways to do this and a number of tools available to you but nothing out the box with BIDS. I wrote a style-sheet that I can apply to the xml in the dtsxthatdocumentsthe package for me. This takes a bit of time to write but is by far the cheapest and most flexible!! There are tools out there that generally give you free trials that allow you toevaluate the tool and the cost of theseare usually pretty reasonable should you choose to buy it. An example of one such tools is: http://software.techrepublic.com.com/download.aspx?docid=279849 Hope this helps... Sam
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2008 12:53pm

Hey Sam - would you be willing to share this stylesheet with the SSIS community? Having a tool like this would be a great boon to a lot of people, and you might even find others to assist to improve it too. Either way, thanks for the pointers.
March 1st, 2008 6:00pm

BIDocumenter (http://www.bidocumenter.com/Public/Default.aspx) is another commercial option.
Free Windows Admin Tool Kit Click here and download it now
March 1st, 2008 6:52pm

jwelch wrote: BIDocumenter (http://www.bidocumenter.com/Public/Default.aspx) is another commercial option. Unless I've missed something, BI Documeter (which is a great tool all around) does not fulfil the original poster's requirements. He's looking for something that will show the column mappings between the inputs and outputs of the data flow components and I have not found this functionality in BI Documenter.
March 1st, 2008 9:39pm

You are correct, I was thinking of something I read about MetaShare - http://metashare.sourceforge.net/ I'm not positive that it actually does what the OP was requested, but it does seem to trace the column through the components that touch it. Doing an actual input to output mapping for each component would be a neat trick - how would you handle a derived column that combines two input columns and outputs them as a single column? Or, worse yet, a script component? Not saying it can't be done - I've actually looked at putting something together myself. But it would be a lot of work.
Free Windows Admin Tool Kit Click here and download it now
March 2nd, 2008 4:17am

Such a tool would be quite useful; however,I would hope that some sort of logical data map (LDM)was used before writing theSSIS packages! The LDM contains all source-to-target mappings of each attribute (handling splits, combines, lookups,transforms ,etc.) andis usually donein Excel (although a relational database is better).Documenting packages after the fact will not document intent or give you business reasons why such-and-such occurred. An LDM can capture this information and justify why a data element went through A, B, and C transforms. This is especially important if your organization is concerned with compliance regulations (SOX, for example).
March 17th, 2008 12:27pm

Tod McKenna wrote: Such a tool would be quite useful; however,I would hope that some sort of logical data map (LDM)was used before writing theSSIS packages! The LDM contains all source-to-target mappings of each attribute (handling splits, combines, lookups,transforms ,etc.) andis usually donein Excel (although a relational database is better).Documenting packages after the fact will not document intent or give you business reasons why such-and-such occurred. An LDM can capture this information and justify why a data element went through A, B, and C transforms. This is especially important if your organization is concerned with compliance regulations (SOX, for example). Although this is very true, I don't think it lessens the value of the tool that the original poster is looking for. Documenting intent is one thing; documenting the reality that was created to realize that intent is something different. Having both available so that they can be compared seems ideal to me.
Free Windows Admin Tool Kit Click here and download it now
March 17th, 2008 2:54pm

Couldn't agree more - I've found the intent and the reality are often two very different things
March 17th, 2008 4:23pm

BI Documenter Updated Mappings Feature ... It has somewhat capability now to document mappings not sure at what extend you want. http://pragmaticworks.com/help/bidocumenter/scr/SSIS_Features.htm SSIS-Tutorials-FAQs | Convert DTS to SSIS | Document SSIS | SSIS Tasks | Real-time SSIS Monitoring
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2011 11:58am

You are correct, I was thinking of something I read about MetaShare - http://metashare.sourceforge.net/ The last part of the link "Extracting SSIS Metadata" is something like http://www.msteched.com/2010/Europe/BIN308Sincerely SH -- MVP, MCITP 2008, MCTS 2008 & 2005 -- Please kindly mark the post(s) that answered your question and/or vote for the post(s).
April 12th, 2011 3:06pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics