I interviewed a couple guys for a DBA position the other day and I asked one of my usual questions which is simply to discuss xp_cmdshell and its implications. Without hesitation, I got the same answer twice. Both guys gasped and talked about the evils of xp_cmdshell. So I let them go on and then presented them with a couple scenarios that we discussed. And again, all of this just makes me think about true evil and how xp_cmdshell just doesn’t fit. See, this xp was developed for a reason; It filled in the gap on some missing functionality, and it does it very well. In fact, it does it so well, and the gap is so big, that xp_cmdshell gained in popularity and became an instant success. And in fact, it was used too much and this is where it got its bad reputation. Don’t hold that against xp_cmdshell though. Just because everyone recognizes its usefulness doesn’t mean that it’s bad. The problem started because everyone wanted to use it and the security was opened wide allowing damage to be done.
But it’s not evil; it’s just misused. If you keep it locked down there’s no reason why you can’t have a fairly nice relationship with xp_cmdshell. The same goes for cursors. Cursors have also fallen prey to the cmdshell curse. And again, it’s through misuse. So don’t kick either of these out of your shop because so many other devs are stupid. Use them both wisely and they’ll do good things for you.
- Sean McCown
- I am a Contributing Editor for InfoWorld Magazine, and a frequent contributor to SQLServerCentral.com as well as SSWUG.org. I live with my wife and 3 kids, and have practiced and taught Kenpo for 22yrs now.
- ▼ March (5)
- ► 2009 (53)