| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic |
|---|---|---|---|---|---|---|---|
Integration Services Language Reference |
Integration Services Language Reference |
chugugrace |
chugu |
03/14/2017 |
sql |
integration-services |
language-reference |
[!INCLUDEsqlserver-ssis]
[!INCLUDEsqlserver]
This section describes the [!INCLUDEtsql] API for administering [!INCLUDEssISnoversion] projects that have been deployed to an instance of [!INCLUDEssNoVersion].
[!INCLUDEssISnoversion] stores objects, settings, and operational data in a database referred to as the [!INCLUDEssISnoversion] catalog. The default name of the [!INCLUDEssISnoversion] catalog is SSISDB. The objects that are stored in the catalog include projects, packages, parameters, environments, and operational history.
The [!INCLUDEssISnoversion] 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 [!INCLUDEssISnoversion] objects in the catalog by opening [!INCLUDEssManStudioFull]. However you can also use the database views and stored procedures directly, or write custom code that calls the managed API. [!INCLUDEssManStudio] and the managed API query the views and call the stored procedures that are described in this section to perform many of their tasks.
Views (Integration Services Catalog)
Query the views to inspect [!INCLUDEssISnoversion] objects, settings, and operational data.
Stored Procedures (Integration Services Catalog)
Call the stored procedures to add, remove, or modify [!INCLUDEssISnoversion] objects and settings.
Functions (Integration Services Catalog)
Call the functions to administer [!INCLUDEssISnoversion] projects.