Microsoft Sql Server Error 8624
Contents |
Processor Error: The query processor could not produce a query plan. ★★★★★★★★★★★★★★★ BalmukundJuly 15, 20143 Share 0 0 Sometimes we see the
Internal Query Processor Error Sql 2008 R2
below error in SQL Server 2008 R2 SP1 when executing a query internal query processor error the query processor encountered an unexpected in SQL Server Management Studio: ----------------------------------------- Error: 8624, Severity: 16, State: 116. Internal Query Processor Error: The query internal query processor error 8630 processor could not produce a query plan. For more information, contact Customer Support Services. ----------------------------------------- So, how to handle this situation? I am using SQL Server 2008 R2 SP1 specifically,
Query Processor Could Not Produce A Query Plan Because Of The Hints Defined In This Query
because some bugs related to the above problem has been fixed in SQL Server 2005 SP2: http://support.microsoft.com/kb/931329 As I am using SQL Server 2008 R2 SP1, so I should not get this error message, but still I am getting this. So, maybe I am doing something wrong which is not the above bug but something different. Let’s check. I have used the below query (well, the logic of the query is not important here) in my SSMS: ------------------------------------------ select * from (select c2 "c7", c4 "c8", COUNT(1) "c9" from Table1 group by c2, c4) Table2 where (c7) not in (select c7 from (select c2 "c7", c4 "c8", COUNT(1) "c9" from Table1 group by c2, c4) Table2, (select c7 "c11", COUNT(c7) "c12" from (select c2 "c7", c4 "c8", COUNT(1) "c9" from Table1 group by c2, c4) Table2 group by c7 having count(c7)=1) Table3 where Table2.c7=Table3.c11 and Table2.c9>1) ------------------------------------------ The query failed with: Error: 8624, Severity: 16, State: 116 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services The error message means that the optimizer couldn’t generate the query plan at all. But why? What’s wrong with the optimizer? The same optimizer is producing plans for the other queries. First of all, please check whether the stats are updated with Full Scan as the optimizer replies on the stats for generating the best execution plan. We can update them by us
360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://blogs.msdn.microsoft.com/sqlserverfaq/2014/07/15/troubleshooting-error-8624-severity-16-state-21-internal-query-processor-error-the-query-processor-could-not-produce-a-query-plan/ Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/977450 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
MichelDecember 11, 20120 Share 0 0 Problem description: We got some mini memory dump. In side our SQL error log, we can see the error message below https://blogs.technet.microsoft.com/mdegre/2012/12/11/8624-internal-query-processor-error-the-query-processor-could-not-produce-a-query-plan/ Stack Signature for the dump is 0x00000000950A8E26 External dump process return code 0x20000001. External dump process returned no errors.Error: 8624, Severity: 16, State: 116. Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16, attempting to create symptom dump ex_raise2: Exception raised, major=86, minor=24, state=116, severity=16 query processor Interesting link:We found out a similar issue. However, I am in SQL Server 2005 SP4 (9.00.5000.00 (X64)), and the issue below was fixed in SQL 2005 SP2.E.G. FIX: Error message when you run a query in Microsoft SQL Server 2005: "Msg 8624, Level 16, State 116 Internal Query Processor Error: The query processor could not produce a query plan" Cause: We got the internal query processor query from the dump, but you could also get the query with a profiler trace with the events TSQL SQL:BatchCompleted or Stored procedure RPC:Completed with Error and Waring Exception. We the query we are able to reproduce the issue each time. We saw that the dump was generated by statistics stream corrupted (spotted that in the generation script of the objects) Resolution: We run an update statitics with fullscan to solve the issue on all objects called by the query.We run again the query and the issue didn't occur. Michel Degremont | Premier Field Engineer - SQL Server Core Engineer |
Tags Dump SQL Server Comments (0) Cancel reply Name * Email * Website Follow UsPopular TagsSQL Server SSAS Cluster Installation Security SQL Server High Availability Windlows Cluster AMO Powershell DBA TIP Analysis Services Kerberos Replication T-SQL Management Studio DC High Availability Migration SSIS Service Packs Archives November 2013(1) September 2013(1) May 2013(1) April 2013(1) March 2013(3) December 2012(1) October 2012(1) September 2012(1) August 2012(1) June 2012(3) All of 2013(7) All of 2012(30) All of 2011(44) All of 2010(36) All of 2009(23) Privacy & Cookies Terms of Use Trademarks © 2016 Microsoft