We are new to using SSISDB. From the following URL (and others) there seems to be some severe issues associated with that database and maintenance plans. Have these been corrected in Sql 2014 or Sql 2016? If not, we may need to stick with storing SSIS packages in the file system (deprecated)
TIA,
edm2
From http://www.ssistalk.com/2012/07/16/ssis-2012-beware-the-ssis-server-maintenance-job/
"
The entire SSISDB catalog is linked together via foreign keys, most of which are all linked to a single ancestor table – internal.operations....
That’s just one downstream table! This entire process ("SQL Server Maintenance Job") completely, utterly locks up the SSISDB database from any SELECT/INSERT data....
With that said, what does it mean to you? Potentially the cancellation of other SSIS packages that are running at the same time. For us, each and every time the maintenance job runs, packages get canceled. This is not good.
"