The only other thing that I can think of is that it is trying to open a console window for some reason. This will always be a problem, *unless*...

I dunno, this one is a little weird. It sounds like the "two-hop rule" problem, but that should not affect xp_cmdshell, because it executes in a different context anyway....

Silverfox (10/5/2009)

---

Nope I have the same viewpoint as yourself. seems too heavy handed to set that at server level, especially considering...

It has long been noted that SQL Server often has issues with over-parallelization, and in fact, Microsoft often recommends setting the server-wide MAXDOP to about half the number of cores...

Ehh? What's that? Speak-up youngun, we can't hear ya!

😀

You'll probably get more response if you edit your post and add or tags.

Ben Adderson (10/5/2009)

---

RBarryYoung (9/30/2009)

---

So [ code="vb" ] has been removed then? Wow, that's a bummer.

I have tried to replace it with [ code="other" ], unfortunately, "other" seems to mean...

By the way, the easiest...

The question did seem unnecessarily ambiguous: "Check all that apply:" hardly tells us whether we are supposed to check al features or just the new features.

CirquedeSQLeil (9/15/2009)

---

This one made me pause for a sec - i was sure there was a trick somewhere in it (an extra space, some syntax or something). But straightforward...

CirquedeSQLeil (9/15/2009)

---

This one made me pause for a sec - i was sure there was a trick somewhere in it (an extra space, some syntax or something). But straightforward...

Hmm, somehow I missed that Jeff already answered this. Never mind ...

huston.dunlap (10/3/2009)

---

..I will show an example of what I am attempting to do. I have a table with two columns, an ID field, and a pointer field. The pointer field...

Actually, this is a more difficult problem than it at first appears, and there are some open questions...

What's the error message that you get?