Config File Options

BI xPress ›› Features ›› Auditing ››
Parent Previous Next

Configuration File Options


In this section you will learn how to control most of the options of BI xPress Auditing Framework from the configuration file. This article only explains how to generate XML configuration files, but similar techniques can be applied if you are using SQL Configuration (Use Path and Value Property).


Configurable Variables / Properties

The following table lists the most common variables/properties you can configure using SSIS configuration to control various auditing framework functionality.

Variable/Property

Description

Package\User::varSSISOps_DisableBIxAuditing

This variable (introduced in v3.2) controls execution of all event handlers for BI xPress Auditing Framework.  Set this variable to True or -1 if you want to disable auditing framework related code inside all event handlers. Set Package.LoggingMode=2 along with this variable if you want to disable framework completely (See next line).

Property: Package.LoggingMode

This property controls native SSIS Logging

0 = UseParentSetting
1 = Enable Logging
2 = Disable Logging
 
Setting this property to 2 disables real-time Data Flow monitoring.

2017.1 and later:

Package\User::varSSISOps_DisableVarLogging


2016.4 and earlier:

OnPreExecute\User::varSSISOps_DisableVarLogging


OnPostExecute\User::varSSISOps_DisableVarLogging

This variable (introduced in v3.2) controls logging of variable values (in PreExecute and PostExecute Event Handlers in 2016.4 and earlier). Set this variable to True or -1 if you want to disable variable logging (on package pre-execute and/or post-execute in 2016.4 and earlier).

Property: OnVariableValueChanged.Disable

Set this property to true or -1 if you want to disable logging of variable changes.

2017.1 and later:

Package\User::varSSISOps_DisableConnLogging


2016.4 and earlier:

OnPreExecute\User::varSSISOps_DisableConnLogging


OnPostExecute\User::varSSISOps_DisableConnLogging

Set this variable to True or -1 if you want to disable connection logging (on package start/stop events (PreExecute/PostExecute) in 2016.4 and earlier).

OnVariableValueChanged\User::varSSISOps_FilteredVars


OnPreExecute\User::varSSISOps_FilteredVars


OnPostExecute\User::varSSISOps_FilteredVars

Set this variable to a list of variables you want to mask during logging process. You can use a comma separated list and you can use wild-card "*" for pattern matching names that are case in-sensitive.

This option is used to mask variable values during logging process. This option is helpful when you have sensitive data (e.g. varFTP_Password) or the variable value is extremely large to display (e.g. varXML_Document). When masking is enabled, "****" is logged in the Bi xPress Audit Database rather than the actual value of the variable. Note: You can configure a list of variables you want to mask outside the package by configuring "varSSISOps_FilteredVars". There are 3 places where you have to set this value (OnPreExecute, OnPostExecute, OnVariableValueChanged).

2017.1 and later:

Package\User::varSSISOps_FilteredConns


2016.4 and earlier:

OnPreExecute\User::varSSISOps_FilteredConns


OnPostExecute\User::varSSISOps_FilteredConns

Set this variable to a list of Connection Managers you want to mask ConnectionStrings during the logging process inside an OnPreExecute Event Handler. You can use a comma separated list and you can use wild-card "*" for pattern matching names that are case in-sensitive.

This option is helpful when you want to hide certain ConnectionStrings or file paths from users who are using BI xPress Monitoring Console or Reports. When masking is enabled, "****" is logged in the BI xPress Audit Database rather than actual ConnectionString of the specified connection managers. Note: You can configure a list of variables you want to mask outside the package by configuring "varSSISOps_FilteredConns". In versions 2016.4 and earlier, there are 2 places where you have to set this value (OnPreExecute, and OnPostExecute).

2017.1 and later:

Package\User::varSSISOps_DisableDataSrcInfoLogging


2016.4 and earlier:

OnPostExecute\User::varSSISOps_DisableDataSrcInfoLogging

Set this variable to true or -1 if you want to disable logging of Data source related information (e.g. ConnectionName, TableName, SQLCommand, and FileName).

2017.1 and later:

Package\User::varSSISOps_DisableDFTRowCountLogging


2016.4 and earlier:

OnPostExecute\User::varSSISOps_DisableDFTRowCountLogging

Set this variable to true or -1 if you want to disable logging of row count attached with source and destination components (NOTE: when you disable row  count logging using configuration it will also disable data source information logging).

2017.1 and later:

Package\User::varSSISOps_MaxVarCharsToLog


2016.4 and earlier:

OnVariableValueChanged\User::varSSISOps_MaxVarCharsToLog


OnPreExecute\User::varSSISOps_MaxVarCharsToLog


OnPostExecute\User::varSSISOps_MaxVarCharsToLog

Set this variable to configure how many characters will be logged for each variable. Default variable length for logging is 4000, anything after that will be truncated.  A value from zero to 2147483647. In versions 2016.4 and earlier, there are 3 places where you have to set this value (OnPreExecute, OnPostExecute, and OnVariableValueChanged).


Important Note

Most of the options discussed in this section only works if auditing framework was applied using BI xPress v3.2.0 or higher. If you are getting any of the following warnings or errors about package corruption or missing objects because one or more objects referred by configuration were not found in your package, then most likely you are running an older version of auditing framework or certain auditing functionality is disabled. You can eliminate the following warnings/errors by changing Package Property SuppressConfigurationWarnings to True.

To change SuppressConfigurationWarnings property right click package designer surface in BIDS and click Properties. 

Warning loading MyPackage.dtsx: The package path referenced an object that cannot be found: "\Package.Variables[User::varSSISOps_DisableBIxAuditing].Properties[Value]". This occurs when an attempt is made to resolve a package path to an object that cannot be found. C:\SSIS\MyPackage.dtsx 
 



Enable/Disable auditing framework completely without modifying packages

BI xPress v3.2.0 introduced several options to configure various BI xPress Auditing Framework features from configuration file. The following sample config file illustrates how to enable/disable auditing framework using two parameters. Make sure packages have the latest version of auditing framework to use this feature (Must be modified with v3.2.0 or higher). When you disable auditing framework no data will be generated for any package which is configured using the following config file.


<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls all auditing options except real-time Data Flow monitoring.

       0 = Enable Auditing Framework

       -1 = Disable Auditing Framework -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_DisableBIxAuditing].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

       <!-- Following Property controls LogProvider Settings.

       0 = UseParentSetting,

       1 = EnableLogging

       2 = DisableLogging -->

       <Configuration ConfiguredType="Property" Path="\Package.Properties[LoggingMode]" ValueType="Int32">

               <ConfiguredValue>1</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Enable/Disable real-time Data Flow monitoring

Real-time Data Flow monitoring can be disabled by setting LoggingMode Property to "2" and to Enable set value to "1" as below (0=UseParent, 1=Enable, 2=Disable). When you disable real-time monitoring you can't view the Data Flow diagram in Monitoring Console.


<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following Property controls LogProvider Settings.

       0 = UseParentSetting,

       1 = EnableLogging

       2 = DisableLogging -->

       <Configuration ConfiguredType="Property" Path="\Package.Properties[LoggingMode]" ValueType="Int32">

               <ConfiguredValue>1</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Enable/Disable variable logging

Use the following configuration options to enable or disable variable logging.


2017.1 and later:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following setting controls variable change history logging

       0 = Enable Logging of variable changes

       -1 = Disable Logging of variable changes -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnVariableValueChanged].Properties[Disable]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls variable logging when package starts and ends [OnPreExecute = Package Start, OnPostExecute=Package End]

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_DisableVarLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


2016.4 and earlier:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following setting controls variable change history logging

       0 = Enable Logging of variable changes

       -1 = Disable Logging of variable changes -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnVariableValueChanged].Properties[Disable]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls variable logging when package starts and ends [OnPreExecute = Package Start, OnPostExecute=Package End]

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPreExecute].Variables[User::varSSISOps_DisableVarLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_DisableVarLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Enable/Disable connection logging

Use the following configuration options to enable or disable connection logging.


2017.1 and later:

<?xml  version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls connection logging when package starts and ends [OnPreExecute = Package Start, OnPostExecute=Package End]

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_DisableConnLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


2016.4 and earlier:

<?xml  version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls connection logging when package starts and ends [OnPreExecute = Package Start, OnPostExecute=Package End]

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPreExecute].Variables[User::varSSISOps_DisableConnLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_DisableConnLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Mask a list of variables during logging process

You can specify a list of variables as below so they are stored as masked values inside the Auditing Database. Since there are 3 places where the variable value is logged, you have to repeat variable lists multiple times for each event handler as shown below.


<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following parameter contains list of variables to be masked from logging

       you can use comma separated list you can use wild-card "*" for pattern matching

       names are case in-sensitive -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnVariableValueChanged].Variables[User::varSSISOps_FilteredVars].Properties[Value]" ValueType="String">

               <ConfiguredValue>*obj*,file*</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPreExecute].Variables[User::varSSISOps_FilteredVars].Properties[Value]" ValueType="String">

               <ConfiguredValue>*obj*,file*</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_FilteredVars].Properties[Value]" ValueType="String">

               <ConfiguredValue>*obj*,file*</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Mask ConnectionString during logging process

You can specify a list of Connection Managers as below so ConnectionStrings are stored as masked values inside the Auditing Database. Since there are 2 places where connections are logged, you have to repeat Connections multiple times for each event handler as shown below.


2017.1 and later:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following parameter contains list of connections to be filtered from logging

       you can use comma separated list you can use wild-card "*" for pattern matching

       names are case in-sensitive -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_FilteredConns].Properties[Value]" ValueType="String">

               <ConfiguredValue>*FTPConn*,*HRSalary*</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


2016.4 and earlier:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following parameter contains list of connections to be filtered from logging

       you can use comma separated list you can use wild-card "*" for pattern matching

       names are case in-sensitive -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPreExecute].Variables[User::varSSISOps_FilteredConns].Properties[Value]" ValueType="String">

               <ConfiguredValue>*FTPConn*,*HRSalary*</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_FilteredConns].Properties[Value]" ValueType="String">

               <ConfiguredValue>*FTPConn,*HRSalary*</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Enable/Disable DataSource logging (i.e. ConnectionStrings, TableName, SQL Statement, and FileName)

To enable or disable use the following settings. DataSource logging captures source/target connection and data source related information. Data source and target information can be seen on Extract/Load Detail Report


2017.1 and later:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following variable controls datasource information logging

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_DisableDataSrcInfoLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


2016.4 and earlier:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!-- Following variable controls datasource information logging

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_DisableDataSrcInfoLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Enable/Disable row count logging

When row count logging is enabled BI xPress generates code to capture row count for each source and target inside Data Flow. If you want to disable this without reapplying auditing framework then use the following configuration file setting.


Important Note

when you disable row count logging using configuration it will also disable datasource information logging

2017.1 and later:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls row count logging

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_DisableDFTRowCountLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


2016.4 and earlier:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Following variable controls row count logging

       0 = Enable Logging

       -1 = Disable Logging -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_DisableDFTRowCountLogging].Properties[Value]" ValueType="Boolean">

               <ConfiguredValue>0</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


Change number of characters to log for variable value

Starting from v3.2.0 BI xPress doesn't log full values of variables (by default only 4000 characters logged) to increase logging performance. For some reason if you want to change this behavior and want to log full values of variables or log different numbers of characters than the default setting then use the following configuration parameters.


BI xPress 2017.1 and later:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Default variable length for logging is 4000 anything after that will be truncated.

       A number from zero to 2147483647 = Log full variable value. There is one place where you have to set this value (see below) -->

       <Configuration ConfiguredType="Property" Path="\Package.Variables[User::varSSISOps_MaxVarCharsToLog].Properties[Value]" ValueType="Int32">

               <ConfiguredValue>4000</ConfiguredValue>

       </Configuration>

</DTSConfiguration>


BI xPress 2016.4 and earlier:

<?xml version="1.0"?>

<DTSConfiguration>

       <DTSConfigurationHeading>

               <DTSConfigurationFileInfo GeneratedBy="PW\User1" GeneratedFromPackageName="" GeneratedFromPackageID="" GeneratedDate="7/13/2011 12:37:17 AM" />

       </DTSConfigurationHeading>

       <Configuration ConfiguredType="Property" Path="\Package.Connections[OLEDB_BIXPRESS_1].Properties[ConnectionString]" ValueType="String">

               <ConfiguredValue>Provider=SQLNCLI;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BIxPress;Data Source=(local);Auto Translate=False;</ConfiguredValue>

       </Configuration>

       <!--  Default variable length for logging is 4000 anything after that will be truncated.

       A number from zero to 2147483647 = Log full variable value. There are 3 places where you have to set this value (see below) -->

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPreExecute].Variables[User::varSSISOps_MaxVarCharsToLog].Properties[Value]" ValueType="Int32">

               <ConfiguredValue>4000</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnPostExecute].Variables[User::varSSISOps_MaxVarCharsToLog].Properties[Value]" ValueType="Int32">

               <ConfiguredValue>4000</ConfiguredValue>

       </Configuration>

       <Configuration ConfiguredType="Property" Path="\Package.EventHandlers[OnVariableValueChanged].Variables[User::varSSISOps_MaxVarCharsToLog].Properties[Value]" ValueType="Int32">

               <ConfiguredValue>4000</ConfiguredValue>

       </Configuration>

</DTSConfiguration>