The idle CPU condition tells SQL Server Agent when the CPUs are quiet enough to start a job. This post shows where to set it, how the two numbers work and how to create the schedule. It also reads the CPU history of your server in T-SQL, so you can choose values that the server can actually meet.
SQL Agent Job Backslash Puzzle: Why Both Rows Were Deleted
A SQL Agent job backslash at the end of a comment line can turn a one row delete into a delete of the whole table. This puzzle sets up the job, explains the cause and tests the effect in T-SQL. It ends with a safe way to write the step.
Performance Condition Alerts: Warnings Before a Log File Fills
Build performance condition alerts for log usage, tempdb free space, and blocking, with sensible delays and an operator response.
SQL SERVER – SQL Service Not Getting Started Automatically After Server Reboot While Using gMSA Account
My first gMSA test: SQL Service was not started automatically after server reboot, even with automatic startup set. Here is what the event log showed.
SQL SERVER – T-SQL Script to Check SQL Server Job History
SQL Server Agent Job History can be queried from msdb. A New Zealand customer requested this report during our weekly health check.
SQL SERVER – SQL Server Agent Missing in SQL Server Management Studio (SSMS)
A client could not see the SQL Server Agent node, it was missing in SQL Server Management Studio. Here are the possible causes, starting with sysadmin rights.
SQL SERVER – Unable to Start Service SQLSERVERAGENT on Server (mscorlib)
After moving the SQLAgent.OUT path, a client saw: Unable to start service SQLSERVERAGENT on server (mscorlib). Here is one cause of this error and the fix.