A job can run in SQLServerManagementStudio but fails to run in T-SQL

In most cases, Context security issues occur during execution. When executed in SSMS, The T-SQL statement is run under the current login name. But the job is in SQLServ

In most cases, Context security issues occur during execution. When executed in SSMS, The T-SQL statement is run under the current login name. However, in SQL Serv

My practice is to use a high-permission account to run the SQL Server Agent, and have an independent account, and the password cannot expire, otherwise it will not run for a period of time. However, based on the "minimum security principle", it is generally not recommended to use excessive permissions. At the same time, you cannot use the SQL Server Agent to execute a job because the T-SQL job step does not use any proxy. For a T-SQL job step, it is run by default in the security context of the job owner.