Integration Services Language Reference
Applies To: SQL Server 2016 Preview
Topic Status: Some information in this topic is preview and subject to change in future releases. Preview information describes new features or changes to existing features in Microsoft SQL Server 2016 Community Technology Preview 2 (CTP2).
This section describes the Transact-SQL API for administering Integration Services projects that have been deployed to an instance of SQL Server.
Integration Services stores objects, settings, and operational data in a database referred to as the Integration Services catalog. The default name of the Integration Services catalog is SSISDB. The objects that are stored in the catalog include projects, packages, parameters, environments, and operational history.
The Integration Services catalog stores its data in internal tables that are not visible to users. However it exposes the information that you need through a set of public views that you can query. It also provides a set of stored procedures that you can use to perform common tasks on the catalog.
Typically you manage Integration Services objects in the catalog by opening SQL Server Management Studio. However you can also use the database views and stored procedures directly, or write custom code that calls the managed API. Management Studio and the managed API query the views and call the stored procedures that are described in this section to perform many of their tasks.