August 11, 2017 at 1:33 pm
We noticed that a certain package failed to execute through an SQL server agent Job . I wonder whether this may have anything to do with building the SSIS package WITHOUT running the Visual Studio 'as an administrator' . The package runs okay within the Studio or when using the DTExecUI.exe utility.
Could this be a matter of the enhanced server security behavior introduced with SQL Server 2008R2 (and later versions)?
August 11, 2017 at 1:43 pm
blom0344 - Friday, August 11, 2017 1:33 PMWe noticed that a certain package failed to execute through an SQL server agent Job . I wonder whether this may have anything to do with building the SSIS package WITHOUT running the Visual Studio 'as an administrator' . The package runs okay within the Studio or when using the DTExecUI.exe utility.
Could this be a matter of the enhanced server security behavior introduced with SQL Server 2008R2 (and later versions)?
Unlikely. More likely is that the SQL Agent user does not have the necessary permissions to execute all of the tasks in the package.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
August 14, 2017 at 1:27 am
I just checked. The rights on the specific package that is causing trouble is identical for all other packages for the user defined for SQL server Agent.
August 14, 2017 at 5:26 am
blom0344 - Monday, August 14, 2017 1:27 AMI just checked. The rights on the specific package that is causing trouble is identical for all other packages for the user defined for SQL server Agent.
I said nothing about the package, rather about the SQL Agent user.
Is this package doing something different from all the other packages, probably something outside of SQL (eg, accessing a file in the file system, an FTP site, another SQL Server instance ...)?
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply