Integration Services (SSIS) Connections
Microsoft SQL Server Integration Services packages use connections to perform different tasks and to implement Integration Services features:
Connecting to source and destination data stores such as text, XML, Excel workbooks, and relational databases to extract and load data.
Connecting to relational databases that contain reference data to perform exact or fuzzy lookups.
Connecting to relational databases to run SQL statements such as SELECT, DELETE, and INSERT commands and also stored procedures.
Connecting to SQL Server to perform maintenance and transfer tasks such as backing up databases and transferring logins.
Writing log entries in text and XML files and SQL Server tables and package configurations to SQL Server tables.
Connecting to SQL Server to create temporary work tables that some transformations require to do their work.
Connecting to Analysis Services projects and databases to access data mining models, process cubes and dimensions, and run DDL code.
Specifying existing or creating new files and folders to use with Foreach Loop enumerators and tasks.
Connecting to message queues and to Windows Management Instrumentation (WMI), SQL Server Management Objects (SMO), Web, and mail servers.
To make these connections, Integration Services uses connection managers, as described in the next section.
Integration Services uses the connection manager as a logical representation of a connection. At design time, you set the properties of a connection manager to describe the physical connection that Integration Services creates when the package runs. For example, a connection manager includes the ConnectionString property that you set at design time; at run time, a physical connection is created using the value in the connection string property.
A package can use multiple instances of a connection manager type, and you can set the properties on each instance. At run time, each instance of a connection manager type creates a connection that has different attributes.
SQL Server Integration Services provides different types of connection managers that enable packages to connect to a variety of data sources and servers:
There are built-in connection managers that Setup installs when you install Integration Services.
There are connection managers that are available for download from the Microsoft website.
You can create your own custom connection manager if the existing connection managers do not meet your needs.
The following table lists the connection manager types that SQL Server Integration Services provides.
Connects to ActiveX Data Objects (ADO) objects.
Connects to a data source by using a .NET provider.
Reads data from the data flow or from a cache file (.caw), and can save data to the cache file.
Connects to a Data Quality Services server and a Data Quality Services database on the server.
Connects to an Excel workbook file.
Connects to a file or a folder.
Connect to data in a single flat file.
Connect to an FTP server.
Connects to a webserver.
Connects to a message queue.
Connects to an instance of SQL Server Analysis Services or an Analysis Services project.
Connects to multiple files and folders.
Connects to multiple data files and folders.
Connects to a data source by using an OLE DB provider.
Connects to a data source by using ODBC.
Connects to a SQL Server Management Objects (SMO) server.
Connects to an SMTP mail server.
Connects to a SQL Server Compact database.
Connects to a server and specifies the scope of Windows Management Instrumentation (WMI) management on the server.
The following table lists additional types of connection manager that you can download from the Microsoft website.
The connection managers listed in the following table work only with Microsoft SQL Server 2012 Enterprise and Microsoft SQL Server 2012 Developer.
Connects to an Oracle <version info> server.
The Oracle connection manager is the connection manager component of the Microsoft Connector for Oracle by Attunity. The Microsoft Connector for Oracle by Attunity also includes a source and a destination. For more information, see the download page, Microsoft Connectors for Oracle and Teradata by Attunity.
Connects to an SAP NetWeaver BI version 7 system.
The SAP BI connection manager is the connection manager component of the Microsoft Connector for SAP BI. The Microsoft Connector for SAP BI also includes a source and a destination. For more information, see the download page, Microsoft SQL Server 2008 Feature Pack.
Connects to a Teradata <version info> server.
The Teradata connection manager is the connection manager component of the Microsoft Connector for Teradata by Attunity. The Microsoft Connector for Teradata by Attunity also includes a source and a destination. For more information, see the download page, Microsoft Connectors for Oracle and Teradata by Attunity.
For details about how to add or delete a connection manager in a package, see Add, Delete, or Share a Connection Manager in a Package.
For details about how to set the properties of a connection manager in a package, see Set the Properties of a Connection Manager.
Video, Leverage Microsoft Attunity Connector for Oracle to enhance Package Performance, on technet.microsoft.com
Wiki articles, SSIS Connectivity, on social.technet.microsoft.com
Blog entry, Connecting to MySQL from SSIS, on blogs.msdn.com.
Technical article, Extracting and Loading SharePoint Data in SQL Server Integration Services, on msdn.microsoft.com.
Technical article, You get "DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER" error message when using Oracle connection manager in SSIS, on support.microsoft.com.