Warning filtering 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.
Users can filter warnings in one of two ways:
• Code: remove all warnings based on the warning's SSIS Alert Code.
• Keyword: remove all warnings based on a specific word or phrased within its Alert Message.
During package execution, BI xPress ignores any warning that matches the comparison type.
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.
Use the checkbox to select the warning filters to apply to the selected packages. The "Is Default?" checkbox dictates which warnings will always be selected when the auditing framework initially loads.
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.