(Continuation of the Metadata 2.0 Series)
MetaShare does more than expose and help maintain your database metadata. It can also search your SSIS server for packages that are the source of the the columns in your dimensions and facts. By providing a folder on the SSIS server in which to search, MetaShare will automatically generate a document to display information about the column’s lineage inside that package. It lists the SSIS task name, task type, and the description as defined in BI Studio. Spending time and effort fully documenting SSIS packages becomes worthwhile because the data collected inside them becomes available to users.
Hopefully this can get a conversation going about how we can collaborate on our metadata and get it out where it needs to be – in front of the business users.
Please let me know what I have to do to extract my ssis metadata. I have tried to use this component but it didn’t wotk. What do I have to fill in the parameters server name, /databaseServerName:, /areaName: …
Can you please send me an execution example…
Thanks, Ilan
Ilan, if you’ll go to http://metashare.sourceforge.net/ there is a sample run-through including screen shots. See if that helps. If not, post another comment and I’ll get you whatever you need.
I have tried to run MetaShare cmd, but errors shows login failed. I only need to get SSIS metadata, not dimension metadata. The SSIS package is running between 2 Oracle servers in Linux. Any place to input Oracle authentication in cmd, instead of server name only? (OR does MetaShare uses SSIS login info for database?)
In this case, the database server name is Data source or data destination server name?
I am able to get the cmd to run, but it doesn’t generate any links for ssis relationships in my wiki files.
I know for a fact the tables analyzed are used in Data Flows in the SSIS….but no dice.
How can I begin to debug without any errors??