Active Directory ADO.NET Connection Manager
Create an ADO.NET connection manager that uses the .Net Providers for OleDb\OLE DB Provider for Microsoft Directory Services.
Create an ADO.NET connection manager that uses the .Net Providers for OleDb\OLE DB Provider for Microsoft Directory Services.
Drive root level OleDb connections and per package connection references from a metadata table so generated SSIS packages all share the same connection managers.
In this webinar, we will introduce you to BimlStudio, BimlScript syntax, and the fundamentals required for you to follow and understand more advanced Biml topics.
Script the SSIS OData source and OData connection manager in Biml using CustomSsisConnection and CustomComponent elements.
Walks a directory (recursively or top-only) for '.dtsx' files, sourcing the root path from a 'PROJECT_ROOT' environment variable with a hard-coded fallback, then emits one ExecutePackage task per file inside a single master package.
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.
Configure connections to cloud data platforms in BimlStudio
Define ETL as relational metadata, then generate connection Biml from a stored procedure that returns connection name and connection string rows.
Defines a RawFileFormat, a File connection for the cache file, and a CacheConnection bound to both, then uses a CacheTransform in a dataflow to populate the cache so later Lookup components can reuse it across packages.
This Walkthrough presents a very fast technique to build a simple (Truncate and Load) SSIS package by leveraging a SQL Stored Procedure and BIML.
Define the FlatFileConnection, FlatFileFormat, and FlatFileSource needed to read a delimited text file in an SSIS data flow generated from Biml.
Lists every base table from sys.tables and emits a per-table SSIS dataflow that pumps rows through the 'SqlServerPdwDestination' adapter, the path used for an initial historical load when migrating to SQL Server Parallel Data Warehouse / Analytics Platform System.
Use the TheobaldXtractSapConnection and TheobaldXtractSapSource elements to copy a single SAP table into SQL Server with one Biml file.
Extend the metadata layer with multiple source connections and per table column lists, then carry the source connection and column choice through annotations into the load package.
Build SSIS package configurations, connection managers, and parent package variables in Biml when working with the package deployment model.
Works around the absence of 'SqlCommandVariable' on the ADO.NET source by setting the source's 'SqlCommand' property at runtime through an expression bound to a package variable, so the same ADO.NET source can run incremental queries against MySQL or any other ADO.NET provider.
Learn how to 'roundtrip' your SSIS packages between SSDT and BimlStudio, and take advantage of the extended Biml toolsets.
Binds a connection's ConnectionString property to a package variable through a property expression and pairs it with a 'ParentPackageConfiguration', so a calling parent package can push a runtime connection string into the child.
Declares two FileConnections (one for the XML file, one for the XSD schema) and binds the XSD connection's ConnectionString property to a package variable via an expression, so the schema path can be supplied at runtime.
Pin GUIDs on project-level connection managers so regenerated packages keep their bindings to the connection managers they were generated against.