error 8624 severity 16
Processor Error: The query processor could not produce a query plan. ★★★★★★★★★★★★★★★ BalmukundJuly 15, 20143 0 0 0 Sometimes we see the below error in SQL Server 2008 R2 SP1 when executing internal query processor error sql 2008 r2 a query in SQL Server Management Studio: ----------------------------------------- Error: 8624, Severity: 16, State: 116.
Internal Query Processor Error The Query Processor Encountered An Unexpected Error During ExecutionInternal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. ----------------------------------------- query processor could not produce a query plan because of the hints defined in this query So, how to handle this situation? I am using SQL Server 2008 R2 SP1 specifically, 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 using the below command for all the statistics created in the associated tables: ------------------------------------------ UPDATE STATISTICS SchemaName.TableName(StatsName) WITH FULLSCAN; ------------------------------------------ After updating the stats try to run the query. If it still gives the same error, then the cause of the above error can be: 1. The SET operators are not correctly set in the instance. 2. This query is really compl
MichelDecember 11, 20120 0 0 0 Problem description: We got some mini memory dump. In side our SQL error log, we can see the error message below 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 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/ 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 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 https://blogs.technet.microsoft.com/mdegre/2012/12/11/8624-internal-query-processor-error-the-query-processor-could-not-produce-a-query-plan/ 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 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 Availabili
Severity: 16, State: 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services." I have traced this to an insert statement that executes as part of a stored procedure. INSERT INTO ledger (journal__id, account__id,account_recv_info__id,amount) VALUES (@journal_id, @acct_id, @acct_recv_id, @amount) There is also an auto-increment column called id. There are FK contraints on all of the columns ending in "__id". I have found that if I remove the contraint on account__id the procedure will execute without error. None of the other constraints seem to make a difference. Of course I don't want to remove this key because it is important to the database integrity and should not be causing problems, but apparently it confuses the optimizer. Also, the strange thing is that I can get the procedure to execute without error when I run it directly through management studio, but I receive the error when executing from .NET code or anything using ODBC (Access). View 5 Replies Similar Messages: Master Data Services :: Error - Query Processor Could Not Produce A Query Plan Internal Query Processor Error: The Query Processor Encountered An Unexpected Error During Execution. SQL 2005 V9.0.2047 (SP1) - The Query Processor Could Not Produce A Query Plan Internal Query Processor Error Internal Query Processor Error Internal Query Processor Error Random Internal Query Processor Error SQL Server 2005 Error 8630: Internal Query Processor Error SQL Server 7 Error 8630 - Internal Query Processor Error Delete Query Failes On Some Databases With Internal Server Error 8624 The Query Processor Ran Out Of Internal Resources The Query Processor Ran Out Of Stack Space....Please Simplify The Query. Internal SQL Server Error For Nested Query We Get Internal Error When Runing Delete Query An Internal Error Occurred. [ ID = 3639 ] On Delete Que