You can specify to scan all variables, which could take a considerable amount of time. This will open the Variable Scanning Options.
Highlight the variables you want to check for dependencies and then click the Scan Variable Dependency icon.
Open your package in BIDS, and go to the Variables windows. If you’re developing your packages with BI xPress, you can easily discover where your variables are being used if they’re being used at all. One of the difficult aspects of SSIS package development is keeping track of where a variable has been used in an expression or whether a variable is being used at all. To download the trial version of BI xPress, head over to. There’s a host of other improvements and bug fixes in this release. If the file path for a configuration file cannot be found, the configuration will appear underlined and highlighted in red in the Configuration Manager. One of the other nice improvements is the ability to detect invalid file paths for configuration files. Packages that have not started execution are white, packages currently executing appear in yellow, packages that have successfully executed appear in green, packages that have failed are red, and packages that have been stopped are now blue.
Previously it was impossible to tell which packages had been stopped by the end user, but with this improvement it’s not possible to tell which package has been manually stopped by the end user. The stopped packages will now appear highlighted in blue in the Package Execution viewer. One of the major improvements with this release (and to be honest its about time) is the ability to view packages that have been stopped by some external source (i.e. With this release comes a few nice improvements that increase the ease of use. Earlier this month on the 14th, version 3.2.1 of BI xPress was released.
0 kommentar(er)
