Understand what really happens after your agents run

Agent data that could be useful in understanding what happens at runtime

• When does the agent really start to run—on schedule or not at all?
• When does the agent really end its run—as expected?
• How long the agent really runs for—too short? too long? near its max execution time?

Now you know what to look for—study your agent run times and see their effects (load) on a server

1. Select the databases you are interested in and retrieve the agent data within them. Agents will be displayed in the grid.
2. With agentEZ you can see all relevant agent information by scrolling to the desired column in the grid. (Press Ctrl+L to load column details if it's greyed out by default)
The columns that you would investigate are as follows (respectively):
• Last Run Start Date—this shows you exactly when an agent begins running. Compare this information to when it is actually set to run and see if there is any significant discrepancy. Also, see how this agent affects the load on your server.
• Last Run Date—this shows you exactly when an agent ends its runtime. Also, see how this agent affects the load on your server.
• Last Run Duration—this shows you exactly how long an agent has run for. This information give you an indication of whether an agent is running as expected or running too short (or too long). You can also use this information and compare it to the Max execution time timeout setting in the Agent Manager. This could give an indication of whether an agent is being terminated prematurely.
• Agent Logs—this convenience feature is found in the Last Run Date column; ellipses button (...) or in the right-click menu. This button opens the log for that particular agent for your own inspection.