Post reply

Internal Query Processor Error:

  • March 30, 2009 at 11:54 am

    #219576

    We have SQL 2005 SP-2 EE 64-bit. We've been running a job every night for the past 2 years that executes a proc that inserts about 1,000,000 records to a table (it grows slightly larger every day) and then runs an update statement. Until last week it had been running fine. Now, however, we have gotten 2 errors the last 5 job cycles. The error message is

    "Internal Query Processor Error: The query processor encountered an unexpected error during execution".

    Here is the update statement :

    Update StarSchema..Dining_Fact

    Set RESERVED_RESTAURANT_ID_INT = IR.Intake_Restaurant_ID_INT,

    RESERVED_RESTAURANT_ID_INT_ORIG = IR.Intake_Restaurant_ID_INT,

    No_Reservation_Count = 0,

    No_Reservation_Flag = 'No'

    From siebelprod..S_EVT_ACT ACT ,

    StarSchema..Intake_Restaurant IR

    Where ACT.SRA_SR_ID = StarSchema..Dining_Fact.SR_ID

    and ACT.TARGET_OU_ID = IR.Intake_Restaurant_ID

    and ACT.ASSESS_1 = 'Y'

    and Intake_Restaurant_Name not in (select resource_Name from Dining_Resources_That_Are_Not_Restaurants)

    If I rerun the job, then the proc runs fine. There are no errors in the event log. Anyone have any ideas on how to troubleshoot this? The other posts I've seen on this issue seem to be related to SQL 2005 SP1, SQL 2000 or SQL 7.0.

  • March 30, 2009 at 6:47 pm

    #968821

    Try specifying a job log file under the job and see if it logs something helpful ovr there.

    MJ

  • March 31, 2009 at 1:08 pm

    #969379

    Thanks Manu,

    Yes, I did have the output going to a file, but that was the only message that showed up. I also checked the SQL Server log but no information in there either.

  • March 31, 2009 at 2:11 pm

    #969442

    Is there anything else that is running at the same time as this update?

    Bob
    -----------------------------------------------------------------------------
    How to post to get the best help[/url]

  • April 1, 2009 at 6:14 am

    #969761

    No, just this job.

  • April 6, 2009 at 8:37 am

    #972572

    Just an FYI - I've included logic in my job to retry the proc if the error occurs. The job runs fine the second time it runs (although it's an intermittant problem, so sometimes it runs fine the first time). It doesn't solve the problem but at least I don't get beeped in the middle of the night.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply