So a few weeks ago I made a switch from our SSIS 2008 package to the new SSIS 2012 project deployment model. I really love having the new project parameters feature (instead of config files) and I enjoy the ability to encase all the sub packages as one big project...
My biggest issue with the new SSIS 2012 Catalog is SSISDB and it's reporting feature. Since we have packages that runs every minute and uses multiple threads, the SSISDB transaction log fills up FAST. We resolved this issue by changing the database mode to SIMPLE however performance still becomes an issue with this many transactions. We ended up turning off logging for our packages (until something breaks) and this seems to resolve a lot of issues.
So here are my questions thus far:
- Is there a way to make a central SSIS server that host all the projects and have child servers process the ETLs using the child's resources?
- How do you all manage the SSISDB database? Size? Performance?
- This bugs me 'To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report'.. why can't we at least see the last onError message in the Log File Viewer like before? That made stuff so much more simple!
- What the heck is up with the SSIS Server Maintenance Job? It seem to screw everything up for a few hours!
In the end I reverted our major project back to the package deployment model instead of the project deployment model. Any inputs? Thanks!