Step 6: Re-assess network

Chip Andrews, Contributor

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).

    Requires Free Membership to View


 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


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

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

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: