If the query optimizer optimizes multiple queries on multiple schedulers, this problem may generate one or more "non-yielding scheduler" errors in the SQL Server Errorlog file. The memory dump records the context of the problem that the query optimizer does not release the scheduler. Additionally, SQL Server creates a memory dump in the SQL Server log folder. This causes a "non-yielding scheduler" error and some other errors to be logged in the SQL Server Errorlog file. While the query optimizer is waiting for the spinlock, the query optimizer does not release the scheduler.In rare conditions the query optimizer does not obtain the spinlock and keeps holding the scheduler. The spinlock is used to access internal structure to record information about the missing indexes for the query plan. When the query optimizer of SQL Server 2005 generates a query plan, the query optimizer may wait for a spinlock to be released. Note Any system or user-level query can encounter this issue. The only way to make SQL Server functional again is to restart the SQL Server service. When this problem occurs, the server does not respond to any attempted operations.
0 kommentar(er)
