Internal Sql Server Error 8624
Contents |
MichelDecember 11, 20120 Share 0 0 Problem description: We got some mini memory dump. In side our internal query processor error sql 2008 r2 SQL error log, we can see the error message below internal query processor error the query processor encountered an unexpected Stack Signature for the dump is 0x00000000950A8E26 External dump process return code 0x20000001. External dump process
Internal Query Processor Error 8630
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.
Query Processor Could Not Produce A Query Plan Because Of The Hints Defined In This Query
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 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 Availability Windlows Cluster360 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.technet.microsoft.com/mdegre/2012/12/11/8624-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
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error: 8624 Internal Query Processor Error: The query processor could https://social.msdn.microsoft.com/Forums/sqlserver/en-US/59c0e1e0-741d-48c9-9eaf-38b5cc1f57d3/error-8624-internal-query-processor-error-the-query-processor-could-not-produce-a-query-plan?forum=sqldatabaseengine not produce a query plan. SQL Server > SQL Server Database Engine Question 0 Sign in to vote SQL Server 2005 9.0.3161 on Win 2k3 R2 I receive the following http://www.bigresource.com/MS_SQL-Error-8624-Internal-Query-Processor-Error-The-query-processor-could-not-produce-a-query-plan--e5IeRWUc.html error: "Error: 8624, 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 query processor 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 internal query processor 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). Thursday, May 24, 2007 9:48 PM Reply | Quote Answers 1 Sign in to vote I consulted tech support. It was finally classified as a bug. The database was in 80 compatibility and changing it to 90 made the problem go away. The other work around was to set arithabort on. This explained why it worked from management studio and not anywhere else. Apparently management studio has arithabort set to on by default. The following is the case closure confirmation from the MS engineer: PROBLEM: ======= An insert query to a table that has foreign key references cannot generate a plan with error 8624Severity: 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 Query DTSRUN Error On SQL7 With Dual Processor [Query] - Query Designer Encountered A Query Error:Unspecified Error Error Loading Query Execution Plan {query} Query Designer Error Encountered A Query Error DB Engine :: Multiple Execution Of Query Pattern Generates Same Query Plan SQL Server Admin 2014 :: Estimated Query Plan For A Stored Procedure With Multiple Query Statements Query Designer Encountered A Query Error Via Enterprise Manager Stored Procedure Query Optimization -