Does changing the Isolation Level affect the settings for Quoted Identifiers

  • I had a strange problem last night. We updated a report stored procedure and Set the Transaction Isolation Read Uncommitted. And then when the report was run this morning

    we got this error.

    INSERT failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or query notifications and/or xml data type methods.

    Should the isolation level affect this? I am running Sql Server 2005 And Sql Server 2008. I did test it when I first ran it in development and I did not get an error, but production doesn't seem to like it. Is there anything else that can cause this?

    Any thoughts would be appreciated

  • Changing the ISOLATION LEVEL doesn't affect the any other SET options that I am aware of.

    The issue could be that the servers or the databases in dev and production are setup with different SET options though so you'll want to check those. See @@OPTIONS, SET Statements, and Configure User Options

    Jack Corbett
    Consultant - Straight Path Solutions
    Check out these links on how to get faster and more accurate answers:
    Forum Etiquette: How to post data/code on a forum to get the best help
    Need an Answer? Actually, No ... You Need a Question

Viewing 2 posts - 1 through 1 (of 1 total)

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