June 9, 2010 at 9:23 am
Hi All,
We are running SQL 2008 on our production server. What we want to do is disable OSQL by using software restriction policy MD5 Hash. Does anybody know of any problems when doing this?
-Roy
June 9, 2010 at 9:37 am
I don't believe so from the server's perspective, but that doesn't mean some other process isn't.
I'd do this in development first:
- Use file permissions to block access to osql
- Turn on auditing on the osql file for everyone to see if anything hits it.
If that seems okay, I'd turn on auditing on the osql file in production for a period of time before any disabling. Any audit hits should be recorded in the Security event log. That way you'll be able to see if any processes are using it.
K. Brian Kelley
@kbriankelley
June 9, 2010 at 9:44 am
Thanks Brian. We will be doing the testing in QA before we do it in production. All changes to production Env gets tested. I will pass this information regarding Auditing to our Network Admin. (He is better at it than me 🙂 )
-Roy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply