Hi All Gurus,
I am getting an error while inserting in table
INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'.
There has been no change made in the database. It was working till yesterday.
Please help. Thanks in advance
Regards
Sachin Samuel
Hiya
I have recently set up a view with a clustered and a non-clustered index on it (t-SQL is below). To create the view and indexes I set arithabort to on as per the help file articles. However, this setting is causing the following error when my application calls a stored procedure setting values in a table:
The transaction was rolled back for the following reason:
UPDATE 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.
Last Query: MFSetApplicant
I am including 2 columns from the table the sp is trying to update in the view. The sp is a very basic update statement, setting all the values in the table row and using the primary key in the where clause. The sp ran fine with no errors prior to changing the setting of arithabort and adding the view and indexes and has been doing so for the last 5 years.
I have tried setting arithabort to off and the error keeps being thrown. I have tried tracing the transaction and can see nothing wrong with the way the sp is being used or the parameters being passed in. Is there any way to change this setting back to off so I can stop this error being thrown? Am I missing something obvious?
thanks
Code Block
SET NUMERIC_ROUNDABORT OFF;
SET ANSI_PADDING, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL, ARITHABORT,
QUOTED_IDENTIFIER, ANSI_NULLS ON;
Go
CREATE VIEW [dbo].[View_LeadMatching] WITH SCHEMABINDING
AS
SELECT dbo.MFApplicants.ApplicantNo, dbo.MFApplicants.Surname, dbo.MFApplicantContactDetails.PostCode
FROM dbo.MFApplicants INNER JOIN dbo.MFApplicantContactDetails
ON dbo.MFApplicants.ApplicantNo = dbo.MFApplicantContactDetails.ApplicantNo
AND dbo.MFApplicants.MortgageRef = dbo.MFApplicantContactDetails.MortgageRef
GO
----------------------------------------------------------------------
CREATE UNIQUE CLUSTERED INDEX IX_View_LeadMatching_ApplicantNo
ON [View_LeadMatching] (ApplicantNo);
GO
----------------------------------------------------------------------
CREATE NONCLUSTERED INDEX IX_View_LeadMatching
ON [View_LeadMatching] (Surname, Postcode)
GO
Hi,
I was recently experiencing a slowness when executing stored procedures from a .NET Application, but it went fast when executing from Query Analyzer. Research led me to find that by turning ArithAbort ON that it forces the SQL Server to use the same Execution plan whether the request is coming from Query Analyzer or the Application.
My concern now is the effect of ArithAbort. I understand what turning this option does, but I am trying to think of a scenario where turning it on could be bad. Does anyone have any suggestions on what I should be aware of when disabling/enabling ArithAbort or ArithIgnore?
Thanks.
-Brian
INSERT [DELETE] 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.
On local dev machine with SQL Express DB everything works fine. Once moved to shared hosting environment (with adjustments to web.config), insert and delete stored procedures produce the above error.
Made sure that stored procedures SET ARITHABORT ON at the beginning and OFF at the end, without success. Even SET ARITHABORT ON at DB level without success.
Suggestions appreciated
I am calling a stored procedure with the following syntax:
Dim MyCommand1 As New SqlCommand("addprospcus", MyConnection)
MyCommand1.CommandText = "set arithabort on"
MyCommand1.CommandType = CommandType.StoredProcedure
MyCommand1.Parameters.Add(New SqlParameter("@Namecust", SqlDbType.NVarChar, 60))
MyCommand1.Parameters("@namecust").Value = txtProspName.Text.ToString
MyCommand1.Parameters.Add(New SqlParameter("@codeterr", SqlDbType.NVarChar, 6))
MyCommand1.Parameters("@codeterr").Value = Trim(TerritoryList1.SelectedItem.Value.ToString)
MyConnection.Open()
MyCommand1.ExecuteNonQuery()
MyConnection.Close()
This is incorrect, but I can not find the correct syntax for calling my stored procedure but first setting "arithabort on".
Thanks in advance for your assistance.
I wrote a stored procedure and set it as a schedule. it has no problem when I execute this SP in query analyzer. But it will show error when I execute it in schedule job.
I think the main reason is I have created a DDL trigger that will fire when DDL_DATABASE_LEVEL_EVENTS happens. Any solution?
SELECT 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. [SQLSTATE 42000] (Error 1934). The step failed.
Hi,I am getting the following error when I run a stored procedure inwhich I am inserting/deleting data from a view that selects from aremote table.INSERT failed because the following SET options have incorrectsettings: 'ARITHABORT'The first statement in the stored procedure is 'set arithabort on'. Ialso ran 'set arithabort on' before creating the view.I read many articles ragarding the setting of arithabort. I set it forthe connection, for the database (alter database) and above all forthe server (sp_configure) but could not get around the above error.However, when I had made the setting using "sp_configure 'useroptions', 64" I was able to run the stored procedure successfully acouple of times. But, later when I had resest 'user options' to 0 andthen back to 64 just to reproduce the earlier error and confirm thatthe error does not come with the 'user options' to 64 setting I wasgetting the same error.Is there any way by which I can overcome the problem?Thanks,Iqbal
View 3 Replies View RelatedInstead of using Full-Text indices, which I don't like to manage, we've tried to use seperate tables that contain recordID, the word, a count of the word in the parent field and computed column which is the CHECKSUM() of the word column. I indexed the checksum column with a clustered index.
Works great in Query Analyser. But when the ASP page calls it, I get this message:
Microsoft OLE DB Provider for SQL Server (0x80040E14)
INSERT failed because the following SET options have incorrect settings: 'ARITHABORT'.
Same for updates and deletes. The question is how should these SET settings be done? Any ideas would be greatly welcomed.
Thanks
Jason
Hi
I am currently running the following query from Query Analyser, I am connected to Server_A and inserting records into
Server_B.Database_B.dbo.MyTable from Server_A .Database_A.dbo.TableRef
Insert into Server_B.Database_B.dbo.MyTable(Field1,Field2,Field3)
Select Field1_Ref,
Field2_Ref,
Field3_Ref
from Server_A .Database_A.dbo.TableRef
However Server_B.Database_B.dbo.MyTable is referenced within an Indexed View and whenever I run this query I get the following error:
Msg 1934, Level 16, State 1, Line 1
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 have tried setting ARITHABORT to ON & OFF within the Query and within the database properties but still recieve the same error.
Does anyone have any ideas on why this would not work?
Thanks