Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

service pack on cluster Expand / Collapse
Author
Message
Posted Wednesday, June 19, 2013 4:10 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Monday, September 19, 2016 10:45 AM
Points: 1,952, Visits: 3,672
Thanks much,

Post #1465420
Posted Thursday, June 20, 2013 3:40 AM


SSCrazy Eights

SSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy EightsSSCrazy Eights

Group: General Forum Members
Last Login: Monday, September 12, 2016 11:57 AM
Points: 8,234, Visits: 16,382
Elliott Whitlow (6/19/2013)
It is my understanding that the system databases get upgraded when SQL starts for the first time with the new (updated) binaries. It can tell internally that the system version of the objects is different. Also in some cases the system objects are unchanged in the database.

Clearer?

CEWII

In fact, a copy of the MSSQLSystemResource database is now located on each node instead of the shared drive and holds the current version of the installed binaries. This is how SQL Server knows whether to perform a rolling upgrade\downgrade on the instance when it starts.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1465543
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse