May 18, 2016 at 8:50 am
We have an automated tool which will apply security updates against a server or workstation. It's been configured to only apply non-SQL Server updates, but last night that was changed. I am seeing items like the following, indicative of an upgrade, in the error log:
Starting execution of PRE_MSDB.SQL
Starting execution of PRE_SQLAGENT100.SQL
Starting execution of MSDB.SQL
Starting execution of MSDB_VERSIONING.SQL
Starting execution of Alwayson.SQL
Starting execution of MSDB_POST_INSTALL.SQL
Starting execution of UPGRADE_UCP_CMDW_DISCOVERY.SQL
Starting execution of SSIS_DISCOVERY.SQL
Starting execution of SSIS_HOTFIX_INSTALL.SQL
But the version of the database is the same before & after:
Microsoft SQL Server 2014 - 12.0.4213.0
Are these entries in the logs indicative of a CU having been [accidentally] applied? I've only upgraded between service packs in the past, and that's where I've seen similar messages in the error log, but the version number has always incremented in those cases.
--=Chuck
May 18, 2016 at 1:24 pm
Confirmed, it was a Cumulative Update. So I guess I still have a question ... when does a CU not result in a change in the SQL Server version number?
In this case, I opened the last error log where the instance was rebooted, and compared it to the current error log, as well as @@version. They all three match.
--=Chuck
May 18, 2016 at 7:47 pm
I manually failed over to the patched server in the cluster, and the version on that server shows the SP1-CU6 in the version. So that sort of answers my question, I was running on the unpatched version this morning. But, that brings up some definite confusion.
If SERVER_A was patched last night, followed by a reboot, causing failover onto the unpatched SERVER_B, why did I see the upgrade-related content in the Error Logs this morning? I am assuming SERVER_B wrote those logs, and I verified that the version number noted was the pre-CU version.
Adding to my confusion, after the manual failover just now to the patched SERVER_A, I am seeing the upgrade-related content in the error logs again.
I'm obviously very green when it comes to Clustering, so thanks for the help.
--=Chuck
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply