To run an SSIS package as a different user (e.g. `tasca\administrator`), follow these steps:

USE [master];
CREATE CREDENTIAL [ssis_cred_admin]
WITH IDENTITY = N'tasca\administrator',
     SECRET = N'YourDomainPasswordHere';

USE [msdb];
EXEC sp_add_proxy 
    @proxy_name = N'SSIS Proxy Admin',
    @credential_name = N'ssis_cred_admin';

EXEC sp_grant_proxy_to_subsystem 
    @proxy_name = N'SSIS Proxy Admin',
    @subsystem_id = 11;  -- SSIS

EXEC sp_grant_login_to_proxy 
    @login_name = N'MySqlAgentJobLogin', 
    @proxy_name = N'SSIS Proxy Admin';

• Type: SQL Server Integration Services Package
• Run as: SSIS Proxy Admin

—

• Open SSIS package in Visual Studio/SSDT
• Go to SSIS → Logging…
• Choose provider (Text file, SQL Server, SSISDB)
• Enable events:
  • `OnError`, `OnWarning`, `OnPre/PostExecute`, `OnTaskFailed`

• Job Properties → Steps → [Your Step] → Edit
• Go to Advanced tab
• Set Output file:

    C:\SSISLogs\MyJobOutput.txt
    

dtexec /FILE "path_to_package.dtsx" /DECRYPT password /REPORTING E D I > "C:\SSISLogs\ssis_debug.txt"

—

• Go to: SSMS → SSISDB → [Project] → [Package]
• Right-click → Reports → All Executions
• Click execution → Messages tab

—

• Error:

    NT SERVICE\SQLSERVERAGENT does not have access to 'MAGNUS_SITD'
    

  → The job step is likely not using the proxy correctly.

• Test with `CmdExec` job step and `dtexec` for clearer logs.
• Check Windows Event Viewer (Application log).
• Check SQL Server Agent job history and output files.
• Use `whoami` inside SSIS Script Task to verify run context.

—

DROP CREDENTIAL [ssis_cred_admin];
EXEC sp_delete_proxy @proxy_name = N'SSIS Proxy Admin';