Step 6: Re-assess network

Learn about re-assessing your network after deploying patches and hotfixes.

As a double-check, you should re-assess the network (as outlined in part one) to ensure that all patches were properly deployed. There are many reasons why deployments fail including mismatched patches (placing an MSDE service pack on a SQL Server instance, for example), locked files and attempting to apply hotfixes to the wrong service pack level. If you chose a non-interactive deployment strategy -- i.e., remote deployment -- then...

you may not have seen the interactive messages signifying the aforementioned problems (as most of the installers will warn you of mismatches).


HOW TO PATCH SQL SERVER, PART 2

 Home: Introduction
 Step 1: Segregate your scan results
 Step 2: Obtain service packs and prepare for deployment
 Step 3: Deploy service packs
 Step 4: Obtain hotfixes and prepare for deployment
 Step 5: Deploy hotfixes
 Step 6: Re-assess network
 Step 7: Plan next assessment
 Back: How to patch SQL Server, part 1

 

ABOUT THE AUTHOR:
Chip Andrews is the director of research and development for Special Ops Security Inc. and the founder of the SQLSecurity.com Web site, which focuses on Microsoft SQL Server security topics and issues. He is also the author of SQL Server Security.

Dig deeper on SQL Server Database Modeling and Design

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchBusinessAnalytics

SearchDataCenter

SearchDataManagement

SearchAWS

SearchOracle

SearchContentManagement

SearchWindowsServer

Close