Deploying Software Updates and Patch Management
- When updating SQL Server it is important that you update all features associated with a SQL instance at the same time.
Before Deploying Updates
- Back up the master, msdb, and model databases
- Back up Analysis Services databases, configuration file, and repository.
- Verify that system databases have sufficient free space if they are not configured for autogrowth. Run the sp_spaceused stored procedure on the master and msdb databases to determine the amount of free space available we need at least 500KB
- Stop services and applications that make connections to SQL Server 2012
Each instance on a server has its own separate program files. We can control which instances you update by using the update’s graphical installer or by launching the update from the command line. Examples below:
<package_name>.exe /qs /IAcceptSQLServerLicenseTerms /Action=Patch /InstanceName=ALTERNATE
To update all instances of SQL Server 2012 on a host computer and all shared components, we would use the option of “/AllInstances” or to update SQL Server shared components only, without updating specific database instances, we would use the option “/Action=Patch”.
To remove updates from a specific instance and all shared components it would simply be “/Action=RemovePatch” although when removing updates, ensure that you remove updates in the reverse of the order in which you applied them.
KEY POINTS TO REMEMBER
- SQL Server 2012 supports up to 50 instances on a single host and up to 25 instances on a failover cluster.
- All features associated with a SQL Server 2012 instance must be updated at the same time.
- Shared features must be updated to the most recent update.
- To update a specific instance use the /InstanceName parameter
- To update all instances then use the /AllInstances parameter