Best Practices

BI xPress ›› Features ››
Parent Previous Next

Best Practice Analyzer


The Best Practices Analyzer inspects SSIS packages and displays recommendations based on best practices.


Feature Highlights

  Investigate packages for adherence to best practices ad hoc as well as in batch mode.

  Store the results of the best practices analysis within the BI xPress database for later analysis.

  Store the results of the best practices analysis within an XML file using the command line.

  Determine package performance issues and potential bottlenecks when using certain predefined best practices.


Important Note:

Pragmatic Workbench (32-bit) must be used when analyzing SSIS packages on a machine that only contains SSDT for Visual Studio 2015.


Table of Contents

  Command Line

  User-Defined Best Practices

o   Path Builder


Tutorial Video


Important Note:

While selecting a technology type to be analyzed within BI xPress Best Practices, you may run into an issue where the source type you wish to analyze does not show up. If this happens, chances are you have not met the system requirements for that specific provider. Please check the System Requirements page and ensure you have all of the system requirements for that specific provider installed properly.


For details on the capabilities of each provider within BI xPress Best Practice Analyzer, click here.


Best Practices Dashboard

From the dashboard you can Create/Modify Best practices or start analyzing for best practice violations.



1.   From workbench: Select the technology type to analyze



2.   Connect to database to access shared rules and store results of analysis

You can connect to any BI xPress database using either Windows Integrated security or SQL Server Authentication. By connecting to a BI xPress database and setting the "Use the BI xPress database" toggle to "On", the results of your analysis will be stored in your database for review at a later time or to compare changes over time. Also, you can save your selected rules to either a local profile or to the database as a "Shared Rule set."  Rules saved to the "Shared Rule set" can be accessed by any user connected to that database


3.   Choose your rules

Select the rule(s) you want to run against the package you selected.


.


4.   Analyze the package(s)

After selecting your rules and choosing your database preference, click "Analyze."  The package will be analyzed using the rule set you created/selected in step 2, and your results will be displayed in the interface as below. This can be opened at any time through the Monitoring Dashboards add-in or by analyzing a new package. Keep in mind that if you did not select to have your results saved in the database, the analysis will not be available after closing the add-in.



Here, you can see the list of packages analyzed on the left. Select a package, and you can see the total violations, errors, performance violations, warnings, and informational messages broken up here. You can toggle which to display or not display by clicking on the name of the type on the right, as well as increase the number of analyses to display at once. At the bottom of this view, you can see the message for each component, and the path for that component as well, to make it easy to correct the violations.


In SQL Server Data Tools 2010 and up:

You can analyze your packages directly from SSDT in SQL Server 2010 and up by right clicking your package or highlighting a number of packages from the solution explorer and clicking "Analyze for Best Practices". This will open each package within SSDT and analyze them. You will follow the same steps as above.