should i stop sql service during windows updates install

windows server os 2008 r2
sql server 2012

Im doing a windows update on a sql server.
it has 1.5 gig of updates including service pack II for sql server.

what should I do to make this update as safe as possible?
should I stop the sql server then run the updates?
I was thinking of doing this to kill any active sql session connections.

is there a way to monitor and disconnect sessions to sql through a gui?
jamesmetcalf74Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Phillip BurtonDirector, Practice Manager and Computing ConsultantCommented:
Here's are two websites with instructions for installing any service pack safely (not just this one):

http://sqlmag.com/database-development/installing-service-pack-2
http://blogs.technet.com/b/beatrice/archive/2009/02/10/best-practices-for-installing-sql-server-service-packs-hotfixes-cumulative-updates.aspx

Definitely: Back up all databases beforehand - and test!

NOTE: There is a regression bug, so there may be a hotfix that you want to install beforehand - see http://sqlblog.com/blogs/aaron_bertrand/archive/2014/06/10/sql-server-2012-service-pack-2-is-available.aspx for more information.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
x-menIT super heroCommented:
On SQL Server Configuration Manager, disable TCP, leave Shared memmory enabled. This will prevent any "outside" connections, and allows "in server" connections.
Do not stop the SQL server service, the update will take care of it.

SQL Service packs should be installed separately from windows server updates, and between reboots.
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
Do not stop the SQL server service, the update will take care of it.
This is the worst thing to do. The update doesn't know if it's some process running and can kill any important task (migration, massive operations with data, etc...). It might ends with a corruption in a database.

If you know that a Windows Update will reboot the machine (generally it does) then you should stop manually the SQL Server. Before stop a SQL Server instance always check for running activities and wait for all processes to terminate before rebooting. Also check for high number of VLF (virtual log files) because can put a database in restore mode for hours, after reboot.

SSMS has a Activity Monitor option. You can check there for the running processes.
0
Eugene ZCommented:
it depends  on your environment and patches details
Normally, you should not stop sql services unless you are on Windows NT sql 4.21 :)
However, in order to avoid any active processes interruptions resulting after post patch reboot  possible long DB recovery\data-db corruption  you may stop services.
Again: it is up to your server activities and patches
Note: sql patches need to have sql server be up and running..
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.