November 1, 2023 at 6:34 pm
Great, glad it helped. You might want to mark my comment as the solution, to potentially help future readers.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
November 1, 2023 at 6:42 pm
ScottPletcher wrote:I would think you would want to use "EXEC AS" on the proc itself rather than inside the proc.
Sadly, without giving IMPERSONATE to the users, I cannot let them us EXEC AS and I don't want them to know what account they are impersonating. That's a large security hole.
I meant when you create the proc they will execute, not them when they exec it.
SQL DBA,SQL Server MVP(07, 08, 09) A socialist is someone who will give you the shirt off *someone else's* back.
November 2, 2023 at 6:05 am
I have just seen this thread. Even though it is now solved it might be useful to refer to the process I documented in SQL FineBuild about setting up SQL Agent proxies. See https://github.com/SQL-FineBuild/Common/wiki/SQL-Agent-Job-Proxy-Accounts
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
November 2, 2023 at 6:07 am
I have just seen this thread. Even though it is now solved it may be useful to look at the process I documented in SQL FineBuild for SQL Agent proxy accounts. See https://github.com/SQL-FineBuild/Common/wiki/SQL-Agent-Job-Proxy-Accounts
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply