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

Spatz, Jason W 96 Reputation points
2021-09-01T20:23:59.893+00:00

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
SQL Server Integration Services
A Microsoft platform for building enterprise-level data integration and data transformations solutions.
2,611 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. ZoeHui-MSFT 38,621 Reputation points
    2021-09-02T08:29:17.323+00:00

    Hi @Spatz, Jason W ,

    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


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.