Query Processor Error
Processor Error: The query processor could not produce a query plan. ★★★★★★★★★★★★★★★ BalmukundJuly internal query processor error the query processor encountered an unexpected 15, 20143 Share 0 0 Sometimes we see the below error
Internal Query Processor Error Sql 2008 R2in SQL Server 2008 R2 SP1 when executing a query in SQL Server Management Studio: ----------------------------------------- internal query processor error 8630 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----------------------------------------- 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.
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members http://www.sqlservercentral.com/Forums/Topic1431107-391-1.aspx Calendar Who's On Home » SQL Server 2008 » SQL Server http://dba.stackexchange.com/questions/22365/sql-server-reasons-not-to-use-default-database-settings-for-ansi-nulls 2008 - General » Internal Query Processor Error 13 posts,Page 1 of 212»» Internal Query Processor Error Rate Topic Display Mode Topic Options Author Message AdmingodAdmingod Posted Thursday, March 14, 2013 10:37 AM SSC-Enthusiastic Group: General Forum Members Last Login: Wednesday, September 28, query processor 2016 4:11 PM Points: 112, Visits: 1,012 Any idea on this...Msg 8624, Level 16, State 21, Line 1Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.we are on SQL Server 2008 R2.Thanks Post #1431107 Lynn PettisLynn Pettis Posted Thursday, March 14, 2013 10:52 query processor error AM SSC-Insane Group: General Forum Members Last Login: Today @ 1:35 PM Points: 23,434, Visits: 37,508 Admingod (3/14/2013)Any idea on this...Msg 8624, Level 16, State 21, Line 1Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services.we are on SQL Server 2008 R2.ThanksSorry, but I can't see what you see. Lynn PettisFor better assistance in answering your questions, click hereFor tips to get better help with Performance Problems, click hereFor Running Totals and its variations, click here or when working with partitioned tablesFor more about Tally Tables, click hereFor more about Cross Tabs and Pivots, click here and hereManaging Transaction LogsSQL Musings from the Desert Fountain Valley SQL (My Mirror Blog) Post #1431121 Orlando ColamatteoOrlando Colamatteo Posted Thursday, March 14, 2013 10:59 AM SSCertifiable Group: General Forum Members Last Login: Thursday, October 6, 2016 8:43 PM Points: 7,932, Visits: 14,339 What build are you on?SELECT SERVERPROPERTY('Edition') AS Edition, SERVERPROPERTY('ProductVersion') AS Product
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 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. 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 - 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 risk when I set these as default settings for my database? E.g. ALTER DATABASE MyDB SET ANSI_NULLS ON and be done with it? Thoughts? Insights? Recommendations? sql-server-2008-r2 share|improve this question asked Aug 13 '12 at 12:56 marc_s 5,42632843 4 No, not at all. In fact, the ability to turn ANSI_NULLS off has a limited life. Soon enough that won't even be an option, it'll always b