Welcome to MSDN Blogs Sign in | Join | Help

April 2006 - Posts

How to tell if your code should be yielding

As we saw in the last post, cooperative clr code that explicitly yields during long-running computations outperforms clr code that gets forcibly rescheduled. How should one discover sql/clr code that is considered 'runaway' by the server and could be

Who says tough guys never yield?

Perhaps you've seen the following note in BOL advising SQLCLR users to explicitly yield in their long-running CLR functions: "Long-running managed code that accesses data or allocates enough memory to trigger garbage collection will yield automatically.
 
Page view tracker