SET ARITHABORT ON: Why (not)?

[Pieter]

Hi,

I recently started using Indexed Views in my SQL Server 2000 (Enterprise
Edition), so I need "SET ARITHABORT ON" when doing an insert or update on
one of the concerend tables.

I was wondering if it would be 'better' to set the ARITHABORT ON for the
database by default, so I wouldn't have to change it everytime, but I'm not
sure if this will have somewhere a negative impact?

Any considerations I have to take in account? Or should I jsut go for it and
SET ARITHABORT ON?

I'ts a 'normal' database, with tables, views, indexed views (1), stored
procedures, and the data in the database are used and manipulated by
Reporting Services and VB.NET 2003-applications.

Thanks a lot in advance,

Pieter

[Uri Dimant]

Hi
This setting is coming along with ANSI_WARNINGS
BOL has pretty good explanations about those settings, have you read it?
"Pieter" <pi**********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...

Hi,

I recently started using Indexed Views in my SQL Server 2000 (Enterprise
Edition), so I need "SET ARITHABORT ON" when doing an insert or update on
one of the concerend tables.

I was wondering if it would be 'better' to set the ARITHABORT ON for the
database by default, so I wouldn't have to change it everytime, but I'm
not sure if this will have somewhere a negative impact?

Any considerations I have to take in account? Or should I jsut go for it
and SET ARITHABORT ON?

I'ts a 'normal' database, with tables, views, indexed views (1), stored
procedures, and the data in the database are used and manipulated by
Reporting Services and VB.NET 2003-applications.

Thanks a lot in advance,

Pieter

[Hugo Kornelis]

On Wed, 24 May 2006 14:13:57 +0200, Pieter wrote:

Hi,

I recently started using Indexed Views in my SQL Server 2000 (Enterprise
Edition), so I need "SET ARITHABORT ON" when doing an insert or update on
one of the concerend tables.

I was wondering if it would be 'better' to set the ARITHABORT ON for the
database by default, so I wouldn't have to change it everytime, but I'm not
sure if this will have somewhere a negative impact?

Any considerations I have to take in account? Or should I jsut go for it and
SET ARITHABORT ON?

Hi Pieter,

I'd go for it, unless you have functionality that depends on the
behaviour of SET ARITHABORT OFF.

Be aware that many front-end tools override various settings for the
connection as soon as the connection is made. Changing the database
options might not be enough - you might have to change the default
connection settings in your front-end as well.

--
Hugo Kornelis, SQL Server MVP

[Pieter]

Yes I read it. Based on the info I found there I don't really see harm in
setting ARITHABORT ON... But I hoped somebody could assure me :-)

"Uri Dimant" <ur**@iscar.co.il> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

Hi
This setting is coming along with ANSI_WARNINGS
BOL has pretty good explanations about those settings, have you read it?

[Uri Dimant]

Pieter
It really depends on your business requiremensts ann would no applied to
every case.


"Pieter" <pi**********@hotmail.com> wrote in message
news:OC**************@TK2MSFTNGP04.phx.gbl...

Yes I read it. Based on the info I found there I don't really see harm in
setting ARITHABORT ON... But I hoped somebody could assure me :-)

"Uri Dimant" <ur**@iscar.co.il> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

Hi
This setting is coming along with ANSI_WARNINGS
BOL has pretty good explanations about those settings, have you read it?