The ability to document SQL Server Agent jobs will be a helpful feature for me. Especially for jobs that run SSIS packages.

Thank you,

Paul S. Waters

Love the diagram portion of BI Documentor but cannot use it since I have to redraw from scratch. Either allow diagrams to be imported to the next snapshot, import SQL Server's diagrams, or maintain file lists across snapshots.

After deploying package(s) I would like to be able to schedule them from BI xPress too

Details about Linked Servers would be helpful because many BI systems reference Linked Servers in ETL solutions found in SSIS or SQL queries.

Check for SSIS best practices for selected packages on demand or automatically in background. There should be an option to enable/disable which best practices you want to check (i.e. Naming convention, Configuration file rules, Security).

This would enable a customer to automate publishing of SSIS code through an an automated process. Ability to hook into DLLs of BI XPress could also enable automation.

In order to have this be a functionally useful as the SSIS OLEDB Destination component we need the ability to be able to create a destination database table based upon the metadata of the SSIS data flow pipeline metadata. This would avoid having to use an OLEDB Destination simply to create the table based on the SSIS data flow pipeline metadata and then turning around and replacing that component with the Task Factory Upsert Destination component.

Provide a new wizard to edit many properties of packages and tasks of selected project or folder/files.

It would be great if we had a Framework that we can apply to all SSIS packages to handle and audit NoMatch Output and Error Output for all Lookups. For example, In some cases we would like to return -1 for NoMatch lookup values and errors and be able to log in a SQL Server table such rows. This will be a great piece of information to add as an exceptions report in BIxPress.

Load documentation from BI Documenter into a WIKI in SharePoint

I don't want high pri emails for success and I may want a different group than failure or warning. I want to be able to choose each alert type differently.

Make it possible to notify different groups of people depending on the outcome of the package.

Have a checkbox in the deployment utility that will create a msi installation file for my packages. Very common that developers are not permitted to deploy and to have a package that can depoy all changes that can be handed to DBA would be great.

Destination to load a fact table and do the surrogate key lookups.

It would be great to have a search feature that would search through all of the packages in a project. This would be able to find things like variables, expressions, and task names.

Right now BIDoc documents all level of information except server level. It would be helpful to see logins and other server level settings in the report.

Add an option to apply the same chosen action across all columns. Will save MUCH time as opposed to choosing the same option for each column.

It would be great to be able to have a Data Cleansing / Data Quality Framework, leveraging on Task Factory TD Data Cleansing Component in which a set of data cleansing rules can be applied after all Source components. For example, after every OLE DB Source, add TF Data Cleansing to remove leading and trailing spaces, convert blank to Null, remove NonNumerics, validate values with a regex, etc..

With a Data Cleansing Framework, you can apply it to all packages, instead of doing this one package at a time.

After the audtting framework is applied, how about iterating through all of the data flows and resetting them to use Format->Auto Layout -> Diagram or do something... they look like spaghetti after your done.