Skip to main content

Apply Service Pack Pre and Post steps


Implementation Plan
1.
Take backup of system registry
2.
Take backup of system databases and user databases
3.
Take backup of settings at SQL Server level
4.
Script out logins and jobs
5.
Take backup of resource database
6.
Make sure that we have the existing level (services packs and cumulative updates readily available). Useful incase of rollback
7.
Make a note of existing SP and patches and resource db version
8.
Install SQL Server service pack
9
Verify the installation logs
10.
Verify that all components and resource database are upgraded to the latest service pack level
11.
Reboot the server
12.
Check connectivity from within the server and outside the server also
13.
Ask the application teams to check connectivity with SQL Server
Roll back plan
1.
Uninstall the SQL Server
2.
Reboot the server
3.
Re-install SQL Server and apply all the previous service packs and cumulative updates to make the versions match
4.
Reboot the server
5.
Verify the installation logs
6.
Take the sql server in single user mode and restore master database
7.
Restore system databases and user databases
8.
Check consistency of databases
9.
In case of any issues reapply the login script and jobs scripts and restore sql server settings
10.
Check connectivity from within the server and outside the server also
11.
Ask the application teams to check connectivity with SQL Server

Comments

Unknown said…
i came to know about this from one of my friend. Really good piece of work
rmouniak said…
It is very good blog and useful for students and developer , Thanks for sharing

Sql server DBA Online Course Banalore

Popular posts from this blog

Self Introduction and Responsibilities of a SQL Server DBA.

Hi, Self Introduction:                      I am Vang chew bigger , currently I am working with   Citronics , Here my role is SQL Server Database Administrator , I am having 3+ yrs Exp in SQL SERVER DBA with T-SQL, I have experience on SQL Server 2000, 2005 and 2008, I have a great experience on installation and configuration of SQL SERVER versions, and also applying the patches, hot fix, services packs and RTM’s accordingly, involved in upgrading on in place and side by side as per client requirement, and also Migrating the database on SQL SERVER 2000 to 2005 and 2008, Solid experience on configuring and maintenance of High availability SQL Server solutions, including Log shipping, Database Mirroring, Replication(Transactional and Merge) and SQL Server Clustering., having experience on performance tuning on server level, database level and query level, Responsible for working with application developers in identifying, resolving and proactively working to prevent performance or oth

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step.

SQL Server 2016 Windows Server 2016 Firewall Rule Step-By-Step. Opening Firewall in SQL Server 2016. Once the SQL Server is installed on the machine. We must enable the incoming traffic i.e., from the application to the SQL Server Database. For this purpose, we must create rule for SQL Server ports so that the application can connect to database & perform the CRUD operations on the tables. Now Let’s start Step-by-Step to enable it. 1.   Start System and Login (As Administrator); 2.   Open Control Panel. Click on Windows Firewall; 3. Now click on Advanced Settings; 4. Windows Firewall console open. If you click on Properties (right side) – you can disable firewall for all networks. We going to Inbound Rules (left side) for our rule creation; After Clicking on the Inbound rules. We will see the below screen.  Click on New

Shrinking a SQL Server Log File with Database in Always ON Availability.

Shrinking a SQL Server Log File with Database in Always ON Availability.                    Once we had a situation in our production server that the database which is in Always ON Availability group has been grown to the maximum size.  Many of them say that we can't shrink the log file as the database is in Always ON and we should take the downtime to perform the operation. But we shrink-ed the database log file to 5 GB from 180 GB. Steps are as below: --To Check the Number of pages allocated by the LogFile. DBCC LOGINFO --To check the file sixe sp_helpdb [SQLPantry] --To check the Log file Size DBCC SQLPERF(LOGSPACE) The above statement will show the logspace of all db at present situation. --To check the Log_reuse_wait description of a log file. select log_reuse_wait_desc,* from sys.databases The above statement will show the status of the log whether it has to be backuped i.e., LogBackup, Nothing, Active Transaction.  When ever there is status as Activ