ssis_proxy_verbose_logging_cheat_sheet
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| ssis_proxy_verbose_logging_cheat_sheet [2025/06/30 14:40] – created oso | ssis_proxy_verbose_logging_cheat_sheet [2025/06/30 14:47] (current) – oso | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| === 🛠️ Running SSIS Job Steps as a Proxy === | === 🛠️ Running SSIS Job Steps as a Proxy === | ||
| - | To run an SSIS package as a different user (e.g. `tasca\administrator`), follow these steps: | + | To run an SSIS package as a different user (e.g. '' |
| == 1. Create Credential == | == 1. Create Credential == | ||
| Line 9: | Line 9: | ||
| USE [master]; | USE [master]; | ||
| CREATE CREDENTIAL [ssis_cred_admin] | CREATE CREDENTIAL [ssis_cred_admin] | ||
| - | WITH IDENTITY = N'tasca\administrator', | + | WITH IDENTITY = N'domain\administrator', |
| | | ||
| </ | </ | ||
| Line 38: | Line 38: | ||
| * Type: **SQL Server Integration Services Package** | * Type: **SQL Server Integration Services Package** | ||
| * Run as: **SSIS Proxy Admin** | * Run as: **SSIS Proxy Admin** | ||
| + | |||
| + | <WRAP center round important 60%> | ||
| + | You’re not creating a new user — you're just wrapping sa in a credential and proxy. A credential is a way to associate a username and password with a proxy in SQL Server Agent. You’re essentially telling SQL Server, “Here’s how to impersonate ' | ||
| + | </ | ||
| --- | --- | ||
| Line 48: | Line 52: | ||
| * Choose provider (Text file, SQL Server, SSISDB) | * Choose provider (Text file, SQL Server, SSISDB) | ||
| * Enable events: | * Enable events: | ||
| - | * `OnError`, `OnWarning`, `OnPre/ | + | * '' |
| == 2. Enable Output File in SQL Agent Job Step == | == 2. Enable Output File in SQL Agent Job Step == | ||
| Line 54: | Line 58: | ||
| * Go to **Advanced tab** | * Go to **Advanced tab** | ||
| * Set Output file: | * Set Output file: | ||
| - | | + | < |
| - | C: | + | C: |
| - | </ | + | </ |
| == 3. Use DTEXEC Logging Parameters (if CmdExec) == | == 3. Use DTEXEC Logging Parameters (if CmdExec) == | ||
| Line 88: | Line 92: | ||
| * Error: | * Error: | ||
| < | < | ||
| - | NT SERVICE\SQLSERVERAGENT does not have access to 'MAGNUS_SITD' | + | NT SERVICE\SQLSERVERAGENT does not have access to 'My_Database' |
| </ | </ | ||
| → The job step is likely not using the proxy correctly. | → The job step is likely not using the proxy correctly. | ||
| - | * Test with `CmdExec` job step and `dtexec` for clearer logs. | + | * Test with '' |
| * Check **Windows Event Viewer** (Application log). | * Check **Windows Event Viewer** (Application log). | ||
| * Check **SQL Server Agent job history** and output files. | * Check **SQL Server Agent job history** and output files. | ||
| - | * Use `whoami` inside SSIS Script Task to verify run context. | + | * Use '' |
| --- | --- | ||
ssis_proxy_verbose_logging_cheat_sheet.1751294434.txt.gz · Last modified: 2025/06/30 14:40 by oso