41 docs tagged with "packages"

Drive SSIS processing packages, including stored procedure execution and SSAS database processing, from a tiny metadata model that scales to many tasks.

Drive root level OleDb connections and per package connection references from a metadata table so generated SSIS packages all share the same connection managers.

Introduce BimlScript as a way to iterate over a package template and discuss why splitting a project across tiered Biml files makes sense.

Define BI assets such as tables in one Biml file, then iterate them in a second tiered file to generate truncate-and-load packages from RootNode metadata.

Walk through the first three exercises every Biml learner should complete: a blank package, a project connection, and a truncate-and-reload staging package.

Configure the Lookup transformation in Biml across three patterns: bare bones auto match, explicit column mapping, and routing unmatched rows to a separate output.

How a metadata-driven Biml project replaces hand-built SSIS templates and keeps every package aligned with a single ETL framework.

Drive SSIS package generation from a small metadata schema covering packages, connections, and connection types, then loop over the metadata to emit one package per row.

Use AllDefinedSuccessors at a high tier to apply a default property such as DefaultBufferMaxRows to every Dataflow Task in a project.

Use template Biml objects and a high tier merge file to push template columns and template events onto every other table or package in BimlExpress.

Reuse Biml across files and projects by moving common patterns into a callee file and invoking it with parameters from a caller file.

Build SSIS Change Data Capture initial load and incremental load packages in Biml using the SQL Server CDC components as custom tasks.

Configure a Conditional Split transformation in Biml to route rows to multiple outputs based on expressions, with special handling for XML reserved characters.

Extend a metadata-driven extraction package by emitting per-row containers with truncate, dataflow, and explicit source-to-target column mappings.

Generate one SSIS package per source table with BimlScript, then extend the script to apply per-table WHERE clauses from a metadata table.

Walk through the steps of authoring a small Biml file and expanding it into an SSIS package using the Biml Package Generator in BIDS Helper.

Generate CREATE TABLE statements for an entire staging environment by reading INFORMATION_SCHEMA from the source database and emitting an ExecuteSQL task per table.

Define SSIS variables in Biml at different scopes and reference them from tasks and parameters within their containing scope.

Use a custom metadata table to control which packages BimlScript generates and which optional transformations they include.

Use BimlScript and a small C# loop to emit one Data Profiling Task per table in a source database, producing per-table profile XML files in a single SSIS package.

Use BimlScript to read a list of source tables from system metadata and emit one extract and load package per table from a single template.

Use a single Biml file to declare a connection and an SSIS package with one or more Execute SQL Tasks, then generate the package directly from the markup.

Build a single SSIS package from Biml using a connection, a control flow task, a data flow with a derived column, and an OLE DB destination.

Generate a master package and a child package with Biml that share an audit run id and a child execution id through parameter bindings.

Architecture overview for a metadata driven SSIS solution that uses Biml and BimlScript to generate table load packages and a master package from a source to target mapping table.

Build SSIS staging packages from a flat file using Biml, then convert hardcoded values into a metadata driven generator that reads file format and column details from a database.

Split a copy-all-tables Biml solution into a driver file and a parameterized package callee so the per-table logic lives in one place.

Configure the OLEDB Command data flow transformation in Biml to execute a parameterized SQL statement for each input row.

Call a stored procedure with output parameters from an OLEDB Command transformation and append the return values onto the data flow buffer.

Use a T-SQL bin packing routine and a BimlScript template to assign tables to balanced parallel containers and generate the matching SSIS package.

Build SSIS package configurations, connection managers, and parent package variables in Biml when working with the package deployment model.

Control SSIS task execution order in Biml using package ConstraintMode and explicit PrecedenceConstraints with logical operators and evaluation values.

Avoid runtime errors when a Biml package uses the same custom script task more than once by giving each instance a unique ProjectCoreName.

Use the Package Importer to convert an existing SSIS dtsx file into Biml when reproducing a specific task or pattern by hand is impractical.

Build SSIS packages that ProcessUpdate every dimension in an SSAS database, either as a single processing task or as one task per dimension inside a parallel container.

Use AMO inside BimlScript to find the most recently processed partitions in each SSAS measure group and emit a Partition Processing task that targets only those partitions.

Generate SSIS packages that process every dimension, the most recent fact partitions, and cube indexes in an SSAS database from a single Biml script.

Pin GUIDs on project-level connection managers so regenerated packages keep their bindings to the connection managers they were generated against.

Use the ForEachAdoLoop control-flow task to iterate over a recordset variable and run multiple SQL tasks per row, with locally scoped loop variables.

Split a Biml solution across tiered files so that connections, packages, and orchestrators can be built in dependency order from a shared RootNode.

Tag generated SSIS packages with Biml annotations and read those tags in later scripts to drive package grouping and master orchestration.