January 28, 2011 at 12:37 pm
I have a proc that's been running fine until now but currently it is returning this error message.
Internal Query Processor Error: The query processor encountered an unexpected error during execution.
The part that fails is this:
select distinct pid
into #temptable
from table1
where memberid in (select memberid from table2 union select 800)
and isnull(checkfield, 'N')='P'
Any thoughts why this would happen all of a sudden?
January 28, 2011 at 4:17 pm
Hi Luk,
I've had a similar problem once, this was caused by a migration from SQL Server 2000 to SQL Server 2005. Assuming that this is not the case in you're situation (you'd mention a migration like this in you're post i'd imagine :-)). Could be related to a space problem in your tempdb maybe?
Willem
January 28, 2011 at 8:06 pm
This has been running since 2006 in 2005 environment. This particular error message appeared for the first time today. This was on SQL 2005 with SP3. We'll upgrade to SP4 and test.
April 8, 2011 at 9:25 am
I had this same problem show up in the following conditions:
* standard table update
* isolated the update to a single string column (varchar(200))
* the column was indexed with Full Text Catalog
* happened on one particular row, others were fine
* SQL 2005 9.00.4053.00 (sp3)
* logging: simple
I was able to fix by dropping and rebuilding the Full Text Catalog.
Hope this helps someone out there.
April 8, 2011 at 9:42 am
We don't use Full Text Catalogs and the problem still exists. We found a temporary workaround but its not the best. I'm not sure why the query processor would fail and how to completely diagnose this problem.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply