The Real MTCS SQL Server 2008 Exam 70/432 Prep Kit- P95: Congratulations on your journey to become certified in SQL Server 2008. This book will help prepare you for your exam and give you a practical view of working with SQL Server 2008. | 452 Chapter 10 Monitoring and Troubleshooting been changed the account might have been disabled by a domain administrator or the account might have expired and auto-disabled itself. All of these issues require that you as the database administrator work closely with domain administrators to find the cause of the issue and resolve it. Figure Locating the SQL Server Agent Job Object Explorer Connect - g Y G S NT SERVICE SQLAgent SQ_iJ 5 sa A Sample_Login S Server Roles B L_J Credentials Bg Sample_Credential E Cryptographic Providers 0 Audits S F 3 Server Audit Specifications B Server Objects E ra Replication E Management J SQL Server Agent B Jobs Qj Job Activity Monitor 1 1 I J Alerts Ba Operators E Proxies E Error Logs J__I 20 The window that opens when you select View History as shown in Figure shows you the job s history. You can view the history of any job by simply checking its corresponding checkbox. When you first view this page you are shown summary information for each time a job was run. As you can see in Figure our sample job was run twice and both executions were successful. By clicking the plus sign for each execution you can view the output from each step of the job. Monitoring and Troubleshooting Chapter 10 453 Figure Job History While you can view the history of the job steps if the output is long you will not get the full output. This is because the field that the job step history is logged into has a data type of NVARCHAR 4000 limiting the field to 4000 characters. As you can see from Figure the fourth time the job was run there was a problem with execution. By expanding the failed job execution we can see the failure reported by job step. If we scroll down in the lower right pain of the window we can see the error message that was reported when the command was run. As shown in Figure there was a login failure for this account because the account was either deleted or the password stored within .
