Execute Package Task
The extends the enterprise capabilities of Integration Services. The letting packages run other packages as part of a workflow.
MSBI Execute Package Task Training in Hyderabad
- Breaking down complex package workflow. This task lets break down workflow into many packages. which are easier to read, test, and maintain. The loading data into a star schema build a separate package for each dimension and the fact table.
- Reusing parts of packages. Other packages reuse parts of a package workflow.
- Grouping work units. Units of work encapsulated into separate packages. The joined as transactional components to the workflow of a parent package.
- Controlling package security. Package authors need access to only a part of a multipackage solution. By separating a package into many packages. The provide a greater level of security, grant an author access to only the relevant packages.
that other package is generally referred to as the parent package. the packages that a parent workflow runs called child packages.
Integration Services includes tasks perform workflow operations. such as executing executables and batch files.
The Execute Package task run child packages. that contained in the same project that contains the parent package. the select a child package from the project by ReferenceType property. The Project Reference setting the PackageNameFromProjectReference property.
The run packages stored in the SQL Server msdb database. The packages stored in the file system. The task uses an OLE DB connection manager to connect to SQL Server. File connection manager to access the file system.
The Execute Package task run a database maintenance plan. The manage both SSIS packages and database maintenance plans in Integration Services solution. A database maintenance plan is like an SSIS package. The plan include database maintenance tasks, and it is always stored in the msdb database.
If package stored in the file system provide the name and location of the package. The package can live anywhere in the file system. it does not have the same folder as the parent package.
The child package run the parent package, or it can run in its own process. Running the child package in its own process requires more memory. but it provides more flexibility.
the parent and child packages to fail together as one unit. the might not want to incur the more overhead of another process.
the ExecuteOutOfProcess property of the Execute Package task is set to False. the child package runs the same process parent package. If set this property to True, the child package runs in a separate process. This is slow down the launching of the child package. Also, if you set the property to True, you cannot debug the package in an install.
The transaction parent package uses can extend to the child package. so, the work both packages perform committed or rolled back.
Propagating Logging Details
The child package the Execute Package task runs may or may not be configured to use logging. the child package will always forward the log details to the parent package. the Execute Package task is configured to use logging. the task logs the log details from the child package.
Passing Values to Child Packages
The child package uses values passed to it by another package. that calls parent package.
- Parts of a larger workflow assigned to different packages.
- The parent package coordinates tasks in a child package.
- A child package requires access to data that is derived from the parent package. Package Configurations
Integration Services provides a configuration type. the Parent Package Variable configuration passing values from parent to child packages. The configuration built in the child package and uses a variable in the parent package. The configuration mapped to a variable in the child package. the property of an object in the child package. The variable can use in the scripts used by the Script task or Script component.
configure the Execute Package Task to map parent package variables or parameters. The project parameters, to child package parameters. The project must use the project deployment model. the child package contained in the same project that contains the parent package.
Accessing Parent Package Variables
Child packages access parent package variables by using the Script task. the name of the parent package variable on the Script page in the Script Task Editor. the don’t include User in the variable name. the child package doesn’t locate the variable run the parent package.
MSBI Execute Package Task Training in Hyderabad
MSBI Execute Package Task Training in Hyderabad: We provide MSBI Execute Package Task Training in Hyderabad by real time experts. We offer online training.