Seems like the obvious answer is....SSISDB custom logging level + PowerBI. 

We are just starting on that journey now because not only is BiXpress no longer supported but it also demands...

Update:   I ran columnstore reorganize and rebuild and the problem was resolved.   Clearly it was corrupted clustered columnstore index. Scary stuff as it gave our customers incorrect results.  A developer...

So this is the proposed solution for thousands of packages....this is crazy.  Curious why the ssisupgrade wizard won't take care of it.  It's like that tool was never tested with...

I just upgraded from 2016 to 2019 (VS2015 to VS2019) using the method of changing the targetserverversion to SqlServer 2019....and experienced no corruption of connections.  We use only shared project-level...

So you know, I didn't have this problem with SSIS 2012 but its a big problem in SSIS 2016.  And it now has an additional bug - it won't save...

See the review on itcentralstation.com

I suspect at least one of the members involved in discussion is the vendor. This is the worst software I have used in my 3 decade career. I just can't...

The simple solution to the licensing issue was to get 2008 for proc with SA, then you could upgrade to 2012 at no charge and stay on per proc licensing.

We are upgrading a data warehouse to 2012 at this very moment because...we are almost in production (june) and I'd rather bite the smaller impact of regression testing now prior...

I also have same problem - New button isn't hightlighted.

This would seem to indicate that the target connection user doesn't have security to create table in the related database. However...

FYI - I had massive performance issue using oledb connection to DB2 using linked server with sql written inline sqlserver - I switched to using openquery and query went from...