x

I need to tighten the security of an existing SQL Server 2008 R2 by disabling certain Instance level configuration options

I need to tighten the security of an existing SQL Server 2008 R2 by disabling certain Instance level configuration options. For example, CLR, Trustworthy, xp_dirtree, xp_regread etc.

How can I check whether disabling these will affect any of my applications/processes.

This is a production server.

Thanks for you help in advance.

more ▼

asked Aug 06, 2014 at 04:53 PM in Default

avatar image

user-720 (google)
32 2 3 5

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

1 answer: sort voted first

Best way to deal with that is to have a test machine with your applications running on it and do the tests there before you do them in production. If that's impossible (and it shouldn't be), then do a single change at a time on production, wait a full 24 hours for that change to impact your applications, then make another change. That way at least you'll know which change caused the issue.

more ▼

answered Aug 14, 2014 at 10:29 AM

avatar image

Grant Fritchey ♦♦
137k 20 44 81

Grant has it spot on. You need to take the scientific approach. Make a change document, observe and document some more before moving on to the next change / variable.

Aug 14, 2014 at 01:35 PM CirqueDeSQLeil
(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

By RSS:

Answers

Answers and Comments

SQL Server Central

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

Topics:

x215
x7

asked: Aug 06, 2014 at 04:53 PM

Seen: 346 times

Last Updated: Aug 14, 2014 at 01:35 PM

Copyright 2017 Redgate Software. Privacy Policy