Patches and updates

I am in a new shop and was told that they do every month updates and patches on production SQL servers without testing the updates on Development box. Could you please guide me to best practices or things to do before applying any updates & patches on SQL servers? I would highly appreciate it. Thank you.

more ▼

asked Mar 02, 2011 at 10:13 PM in Default

avatar image

434 33 33 38

I would want this rule in writing.

What company can afford to drive against a brick wall and be unconcerned about the consequences? I'd also ask the person who chose this if they also like playing russian roulette.

Mar 03, 2011 at 12:04 AM WilliamD
(comments are locked)
10|1200 characters needed characters left

3 answers: sort voted first

I usually follow this procedure:

  1. Read as much as I can about the patch

  2. Investigate if the patch is affecting my servers (usually it does)

  3. Wait until someone else has applied the patch

  4. Read about any issues from others

  5. Apply the patch in test

  6. Wait a week or two for the testers do do their job

  7. Apply the patch in production

If it's a critical patch I usually override the first steps. I have never been suprised by a nasty issue after a patch

more ▼

answered Mar 02, 2011 at 10:29 PM

avatar image

Håkan Winther
16.6k 37 46 58

(comments are locked)
10|1200 characters needed characters left

Never install SPs or Patches on Production with out proper testing on Dev box.

Keep backup of all the system database and user database before applying patches.

After installing Patches Run the DBCC commands against the datbase.

Monitor your Replication, Log-shipping, Clustering and Mirroring if any.

Test, Test ... Test!

If every thing fine, go ahead with production. Else Rollback or revert whole process.

more ▼

answered Mar 02, 2011 at 10:25 PM

avatar image

10.8k 37 57 51

  • but if it's not a business critical server and you can afford downtim, use backups and are brave, feel free to apply it in production at once, but be prepared to do a lot of extra work. :)

Mar 02, 2011 at 10:46 PM Håkan Winther
(comments are locked)
10|1200 characters needed characters left

I have got a follow up question:- To test the SQL 2005 and 2008 patches, do I need to have a copy of all databases on the test box from production and apply the patches? If so, i don't have any client connection to test the application functionality after applying the patches. And, I will need more resources to backup and restore the production database on the test box. What are your thoughts? Please let me know.

more ▼

answered May 05, 2011 at 09:26 PM

avatar image

434 33 33 38

(comments are locked)
10|1200 characters needed characters left
Your answer
toggle preview:

Up to 2 attachments (including images) can be used with a maximum of 524.3 kB each and 1.0 MB total.

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

SQL Server Central

Need long-form SQL discussion? SQLserverCentral.com is the place.



asked: Mar 02, 2011 at 10:13 PM

Seen: 1263 times

Last Updated: Mar 02, 2011 at 10:51 PM

Copyright 2018 Redgate Software. Privacy Policy