February 9, 2010 at 6:24 am
Does SQL Server ever force Lightweight Pooling Mode on?
I've seen LPM cause a few problems with SQL Server Agent failing to start today.
However, the server should not have had LPM enabled
Are there circumstances when this is forced on by SQL Server - for example this server did have a DB in recovery after a scheduled reboot - could some recovery problem end up with LPM being left enabled as running value?
Craig
February 9, 2010 at 7:08 am
SQL does not randomly change its configuration settings. Someone went in and enabled that feature.
Check the SQL Error log, there will be an entry in there from when the setting was changed.
Date2010/02/09 16:19:43
LogSQL Server (Current - 2010/02/09 12:30:00)
Sourcespid52
Message
Configuration option 'lightweight pooling' changed from 0 to 1. Run the RECONFIGURE statement to install.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
February 9, 2010 at 7:22 am
ok - understood, let me change the question slightly
assuming the configuration was set before the reboot -why would this suddenly prevent SQL jobs from scheduling, opening etc..
February 9, 2010 at 8:51 am
Possibly because they're doing something that doesn't work in fibre mode. There's a number of things that don't. Difficult to say for sure though.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply