September 20, 2018 at 5:28 pm
We are trying to set up the use of TFS to build and deploy SSIS solutions for package execution on a dedicated execution server. I've been posting the details in a thread under "integrated services", but thought I should cross-post it to the TFS experts as well. it seems to me someone should have already accomplished what we are trying to do, and could offer us some advice? (I hope)
https://www.sqlservercentral.com/Forums/1994917/How-to-deploy-SSIS-to-server
Pete
September 25, 2018 at 2:24 pm
petwir - Thursday, September 20, 2018 5:28 PMWe are trying to set up the use of TFS to build and deploy SSIS solutions for package execution on a dedicated execution server. I've been posting the details in a thread under "integrated services", but thought I should cross-post it to the TFS experts as well. it seems to me someone should have already accomplished what we are trying to do, and could offer us some advice? (I hope)
https://www.sqlservercentral.com/Forums/1994917/How-to-deploy-SSIS-to-server
Pete
From the other thread, it doesn't look like this is a TFS issue. Or a CA issue. It's really just related to what Steve started explaining about package protection and then other general security related issues you can run into with packages. The gist of it is in the following article - really the same issues:
SSIS package does not run when called from a SQL Server Agent job step
You'll need to understand security context and permissions for all processes, connections, file system or database access used in the package.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply