Error in SQL server 2000 after the migration (internal query processor error)
I just moved a couple of databases from one instance of SQL 2000 from different hardware to SQL 2000 instance of other hardware and after the move from the application side the app team gets an error -2147217900 - Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information.', 'E', '2UA929041X. Does any one have any idea about this. I took a trace while they were testing and I found out this in the trace. exec usp_DlyPrc_LogProcessEvent '-2147217900 - Internal Query Processor Error: The query processor could not produce a query plan. Contact your primary support provider for more information.', 'E', '2UA929041X An idea or direction on this will be greatly appreciated. Thanks hash
That sounds like a rather serious issue. You might want to open a support call with Microsoft. It could be a hardware problem, corrupt sectors on a disk, bad memory chip, or it might be a database that is corrupt. After the migration did you run consistency checks on the db? If not, I'd start there.
@GrantFritchey, good call on the consistency check, so many of us forget the very important step. @hash, Was your app and database on the same server before the change? Can you fail back to the original server for now while you run dbcc checkdb and so your app folks can work?
Just a quick addition to this. This may not be a hardware or database corruption problem. Is this error occuring ***all*** the time, or just for one query in particular? If it is only for one query, SQL Server may just be having trouble generating an execution plan. This can occur if you have some sort of monstor query with subselects and self joins that wrap the query optimiser into knots and produce this sort of error message. To fix the problem in this case, you would need to either 1. Force a plan via query options like "FORCE ORDER" 2. Re-Write the query to be less complex (break it down into smaller chunks maybe using temp tables) Check out this [Knowledge Base article] talking about this exact problem. It may fit your scenario, either way - good luck! :