Post reply

ARITHABORT Error

  • October 7, 2009 at 11:06 am

    #136330

    Hi,

    I Am getting following error:

    Error Message: Error Message INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'. 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. : System.Data.SqlClient.SqlException: INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'. 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.

    I tried adding these SET, but still getting the error. Any solutions please.

    SET ARITHABORT ON

    GO

    SET CONCAT_NULL_YIELDS_NULL ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    SET ANSI_NULLS ON

    GO

    SET ANSI_PADDING ON

    GO

    SET ANSI_WARNINGS ON

    GO

    SET NUMERIC_ROUNDABORT OFF

    go

  • October 7, 2009 at 11:19 am

    #1062957

    How is the insert being accomplished, actual T-SQL command or inside a stored procedure?

  • October 7, 2009 at 11:48 am

    #1062970

    Insert in done through a stored procedure. Stored procedure does use this view, it just references the table.

    But, the table is referenced in a view, which has a indexed on it.

    Thanks,

    VG

  • October 7, 2009 at 11:53 am

    #1062972

    VG-619426 (10/7/2009)

    Insert in done through a stored procedure. Stored procedure does use this view, it just references the table.

    But, the table is referenced in a view, which has a indexed on it.

    Thanks,

    VG

    The stored proc may not have been created with the SET options set as needed for updating an indexed view.

  • October 7, 2009 at 12:11 pm

    #1062981

    You mean, I should use these SET statements in the stored proc, where the table references are made.

    SET ARITHABORT ON

    GO

    SET CONCAT_NULL_YIELDS_NULL ON

    GO

    SET QUOTED_IDENTIFIER ON

    GO

    SET ANSI_NULLS ON

    GO

    SET ANSI_PADDING ON

    GO

    SET ANSI_WARNINGS ON

    GO

    SET NUMERIC_ROUNDABORT OFF

    Thanks,

    VG

  • October 7, 2009 at 12:12 pm

    #1062982

    That (without the GO's) or ensure the stored procedure is created with those options set appropriately.

  • October 7, 2009 at 12:36 pm

    #1062992

    Thanks Lynn. Let me try this.

    -VG

  • October 7, 2009 at 2:08 pm

    #1063058

    Nope, I added those set statements before create stored proc statement ,but still getting the same error...

Viewing 8 posts - 1 through 7 (of 7 total)

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