Is there a solution to allowing an SSIS package hosted in SQL Server Integration Services to write to a file on a network drive? My understanding is that this is a server hop issue - it only occurs when computer 1 is calling to server 2 (the SQL Server) which is calling to server 3 (the network drive), using Integrated Security.
Here is a good dialog of the issue, dating back to October 2012! I believe it is stating that Kerberos delegation is not supported by SSIS and would not be a resolution to not being able to write to the network.
https://feedback.azure.com/forums/908035-sql-server/suggestions/32909818-with-the-new-ability-to-execute-ssis-packages-from
The last comment made was in 2014 and I don't fully understand the "answer".
Before I ask our IT Department to allow Kerberos Delegation on the server hosting SQL Server, I would like to know if it resolves this issue.
I would be fine with running the package as another user, but that does not appear to be possible.
In short, I want a user to click a button on a program that runs a stored procedure. That stored procedure should do some processing and then write the contents of a table out to a network drive, into a file. The user has access to that network drive.
I would typically have my program do the work, but this code is already in place. I am simply trying to replace xp_cmdshell "bcp.."