Warning Filtering

BI xPress ›› Features ›› Auditing ›› Add-in ›› Options ››
Parent Previous Next

Warning Filtering


Warning filtering tab enables users the ability to exclude specific warnings from logging.  Excluding warnings improves package execution times and lower database use. It also reduces logging clutter by only logging messages important to the user. During package execution, BI xPress ignores any warning that match a filter.



Important Note:

Users will only have access to the Warning Filtering page if they can connect to the BI xPress database using the information configured within the Connection Information tab.


Warning Editor

The Warning Editor allows users to filter out some of the more common warnings from being reported. When creating a new warning filter, users choose between a code or keyword comparison. The comparison type chosen will dictate whether they use the code or keyword property. The description property provides users with a property for describing the warning filter. The description property is not used to determine warning exclusion and has a character limit of a thousand.


Users can filter warnings in one of two ways:

  Alert Code: remove all warnings based on the warning's SSIS ErrorCode.

  Alert Keyword: remove all warnings based on a specific word or phrased within its ErrorDescription.



1.   Server:  Provides the Warning Editor with the name of the Server the BI xPress database is located. By default this will be using the information configured within the Connection Information tab.

2.   Windows Authentication: Controls whether the Warning Editor will use Windows or SQL Server Authentication. By default this will be using the information configured within the Connection Information tab.

1.   User ID: If the user does not select Windows Authentication, the User ID textbox will detail which SQL Server username to use to connect to the BI xPress database. By default this will be using the information configured within the Connection Information tab.

2.   Password: If the user does not select Windows Authentication, the Password textbox will detail the password to be used by the username in order to connect to the BI xPress database. By default this will be using the information configured within the Connection Information tab.


3.   Database: The Database textbox provides the Warning Editor with the name of the database that contains the BI xPress Framework Architecture. By default this will be using the information configured within the Connection Information tab.

1.   If the Database selected does not contain the BI xPress Framework Architecture, users will be prompted to generate the Auditing Framework Architecture within the selected database. By default this will be using the information configured within the Connection Information tab.


4.   Warning Editor Table: Contains the pre-loaded list of Alerts to choose from to filter out from being included within execution logs in the BI xPress database.

1.   AlertID: The Unique Identifier within the BI xPress Database for the current Alert

2.   FilterThisAlert: Allows users to select which alerts they wish to filter out from being included within execution logs in the BI xPress database.

3.   AlertCode: If the user compares based on code, the AlertCode will be used to searched for all matching alerts and excluding them from being logged.

4.   CompareAction:  Used to change the Alert Filter's behavior for comparing alerts within a package execution.

5.   AlertKeyWords: If the user compares based on keyword, the AlertKeywords will be used to search the Alert Message for matches and exclude them from being logged.

6.   AlertDescription: Provides users a location to input their own description or reason for filtering this alert.


Once done configuring the Connection tab with the desired settings, either click on the Connection Information, Logging Options, or Advanced User Defined Logging tab to continue configuring the Auditing Framework, or click the Next button to head to the Summary page to begin the process of adding / re-applying the Auditing Framework.


Important Note:

All users have access to the warning filters present within a BI xPress database. Any changes made to the database's warning filters will affect all users. Only delete warnings that will not have adverse affects on other users.


Additionally, having a large library of warnings will not affect package executions. Only the selected and applied filters could increase package performance.