Lightweight pooling is relevant to multiprocessor environments that have excessive context switching. By flipping the
lightweight pooling switch, you might get better throughput by performing the context switching inline, thus helping to reduce user/kernel ring transitions. The
lightweight pooling option actually causes SQL Server to switch to fiber mode scheduling. CLR execution is not supported under lightweight pooling. You can disable one of two options:
clr enabled or
The following is an example of this option:
exec sp_configure 'lightweight pooling', 1goRECONFIGUREgo
The following is a general recommendation of what to specify based on ...