We recently upgrade SQL server from 2008 to 2014.
We have some SSIS packages. Now we start to use the project deploy model to replace package deploy model.
I found one issue that really frustrating.
That is when executing a package in SSISDB catalog by right click the package and execute, if the package has a source or destination that is on network share or UNC path, then the package failed with Access denied. even I have all permissions to the share.
I searched online it says because when we execute from SSISDB catalog, it caused double hop issue, the fix is to setup SPN and allow Kerberos authentication. Just for this small issue like this , we have to setup SPN and Kerberos, this is a little frustrating.
When we use package deploy mode, we save packages on file system, and never have an issue like this, and we never need to setup spn and Kerberos authentication.
Also in the new deploy model, if I execute that in SQL agent job, it suceeed, there is no issue about double hop, it is only in SSISDB catalog.
Is this known issue, and what is the workaround of that?
Try to use the new model, but don't find much advantages compare with using package deploy model to the file system.
Thanks
SQLFriend