Business Intelligence Markup Language - SQL Server Integration Services Design Patterns - page 452

fault instance of the local SQL Server. Once the Connection metadata is configured, I
added a ConnectionName attribute to the ExecuteSQL tag. My Bim-
lScript.biml file now contains the code listed in Listing 19-4 .
Listing 19-4 . Biml After Adding Connection Metadata
<Biml xmlns=" http://schemas.varigence.com/biml.xsd ">
<Connections>
<Connection Name="AdventureWorks2012"
ConnectionString=
"Data Source=.;Initial
Catalog=AdventureWorks2012;Provider=
SQLNCLI10.1;Integrated Security=SSPI;Auto
Translate=False;" />
</Connections>
<Packages>
<Package Name="TestBimlPackage"
ConstraintMode="Parallel">
<Tasks>
<ExecuteSQL Name="Test Select"
ConnectionName="AdventureWorks2012">
<DirectInput>Select 1 As One</DirectInput>
</ExecuteSQL>
</Tasks>
</Package>
</Packages>
</Biml>
Let's test by regenerating the TestBimlPackage.dtsx SSIS package from
BimlScript.biml . When you attempt to generate the SSIS package, you see a dia-
log that confirms you would like to overwrite the existing TestBimlPack-
age.dtsx SSIS package. When you confirm this intention, the TestBimlPack-
age.dtsx SSIS package is regenerated from the metadata contained in the updated
BimlScript.biml file. Open the TestBimlPackage.dtsx SSIS package: it
should appear as shown in Figure 19-3 .