SQL Server – Query Processor – Error 8624

Background

We were experiencing very slow performance on our DB Server.

Checked Top N Queries to identify possible culprits.

We also noticed quite of blocking and deadlocks.

 

Checked SQL Server Error Log

On the DB Server, we reviewed the error log and noticed exceptions with the tag “Error 8624“.

Listings

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.
ex_raise2: Exception raised, major=86, minor=24, state=1, severity=16, attempting to create symptom dump

 

Error Message In Depth

Impacted Objects are listed besides each Stack Dump.

Here are samples:

Sample 1

Image

errorMessage_1_snipped
Text


2015-11-03 15:25:19.48 spid118     * Input Buffer 255 bytes -
2015-11-03 15:25:19.48 spid118     *   s p _ f i ni s h _ d r i l l 
2015-11-03 15:25:19.48 spid118     *     @studentID = 81711716161
2015-11-03 15:25:19.48 spid118     *   , emailAddress = 'daniel@gmail.com'


 

Resolution

Here are the things you need to do:

  1. Apply relevant latest Service pack and cumulative patches
  2. Review identified Programmable Objects ( Stored Procedures, Views, Functions )
    • Run “Update Statistics” on the dependent tables
    • Re-write queries and attempt to make them less costly
      • Compare revised queries plan cost for each new re-write

 

References

Aggregate or Computed Columns

  1. FIX: Error 8624 may occur with subquery that contains aggregate or computed columns
    https://support.microsoft.com/en-us/kb/290817


TroubleShooting

  1. Troubleshooting : Error: 8624, Severity: 16, State: 21. Internal Query Processor Error: The query processor could not produce a query plan.
    http://blogs.msdn.com/b/sqlserverfaq/archive/2014/07/15/troubleshooting-error-8624-severity-16-state-21-internal-query-processor-error-the-query-processor-could-not-produce-a-query-plan.aspx

One thought on “SQL Server – Query Processor – Error 8624

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s