Microsoft introduced some major changes in SQL Server Integration Services with SQL Server 2012.
Brand new “SSISDB” database launched as SSIS catalog “A New repository database of Integration Services”. This new repository database brings a lot of abilities for developers, testers and administrators.
Prior to SQL 2012 all SSIS packages are stored either in MSDB or in file system. Many times it becomes critical decision to decide where should our package or config files store. This also makes Deployment & administration difficult.
With SSISDB, Packages can be directly deployed to SSISDB using SQL Server Data Tools for BI Studio. Packages keep a deployment history so you can even rollback some revisions of your package.
SSISDB is not installed by default with installation of SQL Server 2012 or above. When you connect to SQL Server using SSMS, you will find new folder “Integration Services Catalogs”. The catalog is not set up by default, you will have to create it.
When you click on create catalog, below window will appear. You need to select enable CLR integration option to use SSIS catalog. Enter the password to protect the database master key that is used for encrypting the catalog data. This password is very important & sensitive, so make sure to remember this password or save it in a secure location. The catalog automatically encrypts the package data and sensitive values. The catalog also automatically decrypts the data when you retrieve it.
When you click “OK”, SSISDB catalog will be created along with SSISDB database. SSISDB created by restoring “<Installation Directory>\MSSQL\120\DTS\Binn\SSISDBBackup.bak”. SSISDBBackup.bak backup file is available in installation directory after successful installation of Integration services. Although SSISDB is created automatically while enabling SSISDB catalog but still it will be considered as User database not as System database,
SSISDB Catalog default reports
SSISDB catalog comes with 4 different reports along with dashboard.
SSISDB catalog Dashboard
Rename SSISDB catalog database
You should not rename SSISDB because it will cause SSISDB catalog inaccessible.
When you rename SSISDB it will delink all your SSIS catalogs & packages. After rename, you will not find any package under “Integration Services Catalogs”. The best part is, when you rename it back to SSISDB, all your catalogs and packages will be visible again without any additional efforts.
Catalogs and Packages unvisible under “Integration Services Catalogs” after rename
Catalogs and Packages visible under “Integration Services Catalogs” after renaming back to original
Manage Size of SSISDB catalog database
Microsoft introduced SSISDB catalog database to keep trace of each execution, project version and other details which is very typical activity prior to SQL Server 2012. But all this thing can make your SSISDB database very large.
You can change SSISDB database catalog configuration to change retention window and other parameters, impacting its size. Catalog properties effect SSISDB database size as below:-
· Clean logs periodically (set to True)
· Retention period (set to specific number of days –the larger the number of days the more prevalent the problem could be)
· Periodically remove old versions (set to true)
· Maximum number of versions per project
Check Catalog Properties using SSMS
Check Catalog Properties using T-SQL
SELECT * FROM SSISDB.CATALOG.CATALOG_PROPERTIES
You can change catalog properties in above SSMS window or like below by using T-SQL
EXEC SSISDB.CATALOG.CONFIGURE_CATALOG RETENTION_WINDOW, <NO.OF DAYS>
SSIS Server Maintenance job
To maintain SSISDB database size according to retention configured above, SQL Server creates “SSIS Server Maintenance job” when we enable SSISDB catalog feature.
The job is responsible of maintaining history as per the retention window and maintains a maximum number of versions per project. Ensure Job is enabled on server.
“SSIS Server Maintenance job” Job has 2 Steps:-
1) Remove operation records
2) Remove old versions per project on basis of set retention
Types of Logging for SSIS server through SSISDB catalog
|Logging is turned off. Only the package execution status is logged.
|All events are logged, except custom and diagnostic events. This is the default value.
|Collects the data required to track lineage information in the data flow. You can parse this lineage information to map the lineage relationship between tasks. ISVs and developers can build custom lineage mapping tools with this information.
|Only performance statistics, and OnError and OnWarning events, are logged.
The Execution Performance report displays Active Time and Total Time for package data flow components.
|All events are logged, including custom and diagnostic events.
Source: According to MSDN https://msdn.microsoft.com/en-IN/library/hh231191.aspx
You can change logging as per requirements using SSMS. If user need some specific logging, Customized logging option is also available.
Reference: Rohit Garg (http://mssqlfun.com/)
You can find and follow MSSQLFUN:-
Other Linked Profiles :-