Database Reference
In-Depth Information
I'll cover the semantics of writing code in each of these tools later in the chapter.
Now, I'll explore some of the other features shared by the Script task and the Script
component.
Project Explorer
Software development elements in Visual Studio are stored in logical groups called
projects. The Visual Studio environment in SQL Server Data Tools (SSDT) will behave
in much the same way; as shown in Figure 3-1 , the file(s) for a given script is represen-
ted in the Project Explorer window. In the same figure, you can see that the project has
a rather lengthy and arbitrary name. This is a system-generated identifier used to
identify the project and the namespace in which it resides, but it can be changed if you
prefer to have a more standardized naming convention in your script.
Figure 3-1 . Script task Project Explorer
It's worth pointing out that the C# and VB.NET code files that you create in Project
Explorer are not physically materialized in your project. Rather, the filenames exist
only to logically separate the code files within the project—the code itself is embedded
inline within the XML of the package (the dtsx file).
Also included in the Project Explorer is a virtual folder named References. In this
folder, you will find the assembly references for core functionality required by the
script. In addition, you can add your own references to this list to further extend the
capability of the Script task or Script component.
Because each instance of the Script task or Script component in your package is
surfaced as a Visual Studio project, you have a significant amount of control over the
properties of that project. Much like a full-featured software development project, an
instance of the Script task or Script component allows the ETL developer the ability to
 
 
Search WWH ::




Custom Search