question

SpatzJasonW-8417 avatar image
0 Votes"
SpatzJasonW-8417 asked SpatzJasonW-8417 commented

Why won't dbo.sysssislog be written to if proxy account is executing the package

So we setup ssis logging in the package - Run the packaged in Studio, no problem writes to table. Publish it to SSIS and run it using the sql server agent account and it again writes to that sysssislog table. However if we run it as a proxy account it no longer writes to that table and isn't generating errors anywhere. The credential for the proxy account has db_owner on the database used in the connection. Even though it has db_owner we granted execute on dbo.sp_ssis_addlogentry on the DB and MSDB just in case. still no dice. If we grant the credential SysAdmin to the server, then it writes out to that table. Obviously we don't want to grant a proxy credential that access, but I am obviously missing a permission SOMEWHERE that allows me to do this. Any ideas!?

Thank you!
Jay

sql-server-integration-services
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

ZoeHui-MSFT avatar image
0 Votes"
ZoeHui-MSFT answered SpatzJasonW-8417 commented

Hi @SpatzJasonW-8417,

You may try to set the account for column-level permissions.

In this way you could give the account permission to write the dbo.sysssislog without granting credential SysAdmin.

Take a reference: filtering-sql-server-columns-using-column-level-permissions

You may have a try to see if it will be helpful.

Regards,

Zoe


If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hot issues October



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for your response! I don't think this will help me in this case, because the account already has db_owner so can write to every table in the database that is being used for the query and the log destination. I am hoping someone knows at the system level what permission is needed. I specifically think this has to do with using a proxy account to run the ssis job. Because I have endusers (who are also not sysadmin and not db_owners) who run the ssis package from studio and they have the right to write to that sysssislog table.

0 Votes 0 ·