Monday, February 13, 2012

ARITHABORT

I have problem with indexed view:
SELECT failed because the following SET options have incorrect settings:
'ARITHABORT'
When insert, also some other options could affects.
I can't change the server properties for all required options because it
affects also other databases which are not mine.
Is there any way to set this option for my connection?
Maybe on SQL or on ado object?
I don't won't to put in each procedure and view the following statement:
SET
ARITHABORT,ANSI_NULLS,ANSI_PADDING,ANSI_
WARNINGS,CONCAT_NULL_YIELDS_NULL,QUO
TED_IDENTIFIERS
ON
SET NUMERIC_ROUNDABORT OFF
Regards,SimonYou can set some of these as default options per database (ALTER DATABASE).
But many of those are
largely useless, as many APIs (mostly the modern APIs) will override the ser
ver/database setting
anyhow. So you can set these setting when you connect from your app. But if
you use connection
pooling, these settings will be reset anyhow when a connection is re-used (G
oogle for
sp_reset_connection). It is possible that your API has option to set these s
ettings, but we'd need
to know what API you are using to tell that (or, rather, search the document
ation for the API).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"simonZ" <simon.zupan@.studio-moderna.com> wrote in message
news:ublg22peGHA.3808@.TK2MSFTNGP02.phx.gbl...
>I have problem with indexed view:
> SELECT failed because the following SET options have incorrect settings: '
ARITHABORT'
> When insert, also some other options could affects.
> I can't change the server properties for all required options because it a
ffects also other
> databases which are not mine.
> Is there any way to set this option for my connection?
> Maybe on SQL or on ado object?
> I don't won't to put in each procedure and view the following statement:
> SET ARITHABORT,ANSI_NULLS,ANSI_PADDING,ANSI_
WARNINGS,CONCAT_NULL_YIELDS_NU
LL,QUOTED_IDENTIFIERS ON
> SET NUMERIC_ROUNDABORT OFF
> Regards,Simon
>

No comments:

Post a Comment