Question:In the SQL Server Error Logs I saw the following message:

The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query

Is there a way to find the query ? I know I can use something like Extended Events which would allow me to trap the sql text , but what about finding a query that has executed and triggered this error

Answer:If you don’t have the query , you can use some DMVs to extract large queries .The limitation is that the data from DMVs is refreshed after every SQL Server restart.

Here are some example queries utilitising DMVs which could assist you to track down the query .

SQL Server Find high impact queries with sys.dm_exec_query_stats

SQL Server Performance Top Queries by Total CPU Time

How to find Longest running queries in SQL Server

Look for queries with long IN lists, an unusually large number of UNIONS & nested sub queries. In my experience these have contributed a large percentage of the reason for these error messages.

On occasion , the root cause may be fixed by a the service pack upgrade.

本文数据库(mssql)相关术语:熊片数据库 mssql数据库 oracle数据库 pubmed数据库 access数据库 万方数据库

主题: SQLCPUSQL Server
分页:12
转载请注明
本文标题:ERROR 8623 The query processor ran out of internal resources and could not produ ...
本站链接:http://www.codesec.net/view/522498.html
分享请点击:


1.凡CodeSecTeam转载的文章,均出自其它媒体或其他官网介绍,目的在于传递更多的信息,并不代表本站赞同其观点和其真实性负责;
2.转载的文章仅代表原创作者观点,与本站无关。其原创性以及文中陈述文字和内容未经本站证实,本站对该文以及其中全部或者部分内容、文字的真实性、完整性、及时性,不作出任何保证或承若;
3.如本站转载稿涉及版权等问题,请作者及时联系本站,我们会及时处理。
登录后可拥有收藏文章、关注作者等权限...
技术大类 技术大类 | 数据库(mssql) | 评论(0) | 阅读(39)