Tag Info

New answers tagged

2

Not a solution, but you can work around the issue by making the job owner a SQL account. Each time a job is started, SQL Server verifies the identity of the job owner and checks that it has permission to execute the job. If the owner is a Windows account, the engine needs to query Active Directory. If for any reason that fails, the job will not run. It ...


1

Try this CREATE TRIGGER Trigger_t1 ON T1 FOR INSERT AS BEGIN SET NOCOUNT ON; insert into T2(C1,C2,C3 ) select C1,C2,C3 from inserted insert into T3(C1,C2,C3 ) select C1,C2,C3 from inserted insert into T4(C1,C2,C3 ) select C1,C2,C3 from inserted END GO DML trigger statements ...


1

I had a similar problem that I just resolved. Turned out, a new group policy had been applied to our server. This group policy disallowed domain users access to the D:, E:, & F: drives. Our SQL Server Agent was configured to write out its error log to the E: drive. As the Log On account for the SQL Server Agent service was a domain based account, SQL ...


4

That check box does not prevent job step history from being recorded/stored. SQL Server is going to do all this by default and that I know of you cannot turn it off. The check box referenced is for telling SQL Agent to store additional or more detailed job step output. It would store this information to msdb.dbo.sysjobstepslogs. Which from my testing just ...


0

Use the SQL Server configuration manager to change the SQL Server Agent user account. Change it to run as local system, apply and restart and then back to the correct user, dont add any privileges to the user in the operating system (esp. not add it to the server local administrator group). The Configuration manager will set all the correct permissions for ...



Top 50 recent answers are included