Integration Services (SSIS) Server
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).
After you design and test packages in SQL Server Data Tools, you can deploy the projects that contain the packages to the Integration Services server.
The Integration Services server is an instance of the SQL Server Database Engine that hosts the SSISDB database. The database stores the following objects: packages, projects, parameters, permissions, server properties, and operational history.
The SSISDB database exposes the object information in public views that you can query. The database also provides stored procedures that you can call to manage the objects.
Before you can deploy the projects to the Integration Services server, you need to create the SSISDB catalog.
For an overview of the SSISDB catalog functionality, see SSIS Catalog.
Like other user databases, the SSISDB database does support database mirroring and replication. For more information about mirroring and replication, see Database Mirroring (SQL Server).
You can also provide high-availability of SSISDB and its contents by making use of SSIS and AlwaysOn Availability Groups. For more information, see this blog post by Matt Masson, SSIS with AlwaysOn, at blogs.msdn.com.
When you connect to an instance of the SQL Server Database Engine that hosts the SSISDB database, you see the following objects in Object Explorer:
The SSISDB database appears under the Databases node in Object Explore. You can query the views and call the stored procedures that manage the Integration Services server and the objects that are stored on the server.
Integration Services Catalogs
Under the Integration Services Catalogs node there are folders for Integration Services projects and environments.