Internal Query Processor Error The Query Processor Could Not Produce
Contents |
Processor Error: The query processor could not produce a query plan. ★★★★★★★★★★★★★★★ BalmukundJuly 15, 20143 Share 0 0 internal query processor error the query processor encountered an unexpected Sometimes we see the below error in SQL Server 2008 R2 internal query processor error sql 2008 r2 SP1 when executing a query in SQL Server Management Studio: ----------------------------------------- Error: 8624, Severity: 16, State: 116.
Internal Query Processor Error 8630
Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. ----------------------------------------- So, how to handle this situation? I
Query Processor Could Not Produce A Query Plan Because Of The Hints Defined In This Query
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 stat
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
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://dba.stackexchange.com/questions/22365/sql-server-reasons-not-to-use-default-database-settings-for-ansi-nulls policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. query processor Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SQL Server : reasons not to use default database settings for ANSI_NULLS? up vote 3 down vote favorite I've been given a case where a customer is experiencing this error internal query processor - once in a while: Msg 8624, Level 16, State 21, Line 1 Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services. They're using our software, and running it on SQL Server 2008 R2 (RTM) and at compatibilty level 100 (SQL Server 2008). The database however was originally created on a 2000 or 2005 machine (can't reproduce anymore) and then moved to 2008 R2 recently. The stored procedure in question has an ugly looking INSERT statement which grabs data from ten (yes!) "copies" of a given table, all joined with RIGHT OUTER JOIN against one another (same table - ten JOINs against it). The one solution I found that seems most appropriate has to do with various settings - it's recommended to use: set ANSI_NULLS ON set ANSI_PADDING ON set ANSI_WARNINGS ON set CONCAT_NULL_YIELDS_NULL ON set QUOTED_IDENTIFIER ON set ARITHABORT ON set NUMERIC_ROUNDABORT OFF OK - sure - I can set these before every stored procedure I create (or alter). My question to the database gurus out there would be: any ris