On Monday (since I’ve worked enough this damned weekend already), I’m going to go through the other two clusters and compare Updates that were installed, and base levels of SQL Server. Here’s the list of Updates applied last night. After the Windows updates were applied, my event logs on ONE server started being spammed with the Agent Alive checks. Last night, the System Administrator applied some Windows Updates (I don’t have a “test” SQL Cluster, but all these updates were applied on our Test SQL Servers prior to last night). Īnyway, so, none of the clusters in my environment have any history of Event ID 53 for SQL Agent. Here’s one connect article that shows some more details and which versions are fixed with what CU’s. Not a one of them ever had the “dreaded” LooksAlive or CheckServiceAlive entries with Event ID 53 from.
They all have (change that to HAD now that I’ve upgraded) SQL 2012 RTM, SQL 2008 R2 SP2, and SQL 2008 SP3. I had read about the issues with the SQL Agent “Is Alive” checks spamming event logs on clustered SQL Server 2012 and SQL Server 2008 R2 SP instances… and since I have three sets of 2 Node clusters running multiple instances including 2012, 2008R, after reading about that a few months back, I checked my servers.
0 kommentar(er)
