I recently came across the same problem and changing the max concurrency to 1 seemed to fix my problem. Hope this help! 😀

/MAXCONCURRENT " -1 "

Looks like this problem has been reopened this year. I had hoped this would be fixed with the SSMS update in SP1, but no such luck...

http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=412929

Here's another article related to this topic.

This article on Tom's Hardware compared the energy consumption of an AMD vs. Intel CPU...

http://www.tomshardware.com/2007/10/19/the_truth_about_pc_power_consumption/

😀

I haven't had this particular problem, but there are some alternatives to using the debugger.

1) Pull the stored procedure contents out and paste them into Query Analyzer; and step thru...

With the wide variety of answers in this discussion, I'm surprised no one has mentioned an alternative to the debugger which should work even if the developers are locked out...

I was lucky enough to get on the beta list for this Transcender product and highly recommend it.

Take care,

Jeff

CD was worthless, best study material for this exam for getting a feel for the new user interface for the 70-100 exam is the Transcender... All the books I've...