Optimization Job and DB Option Settings

Question

Post reply

Optimization Job and DB Option Settings

mssql_rules

SSCrazy

Points: 2783
More actions
August 2, 2004 at 11:43 am

#83516

I see the following error message in my job output file:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1934: [Microsoft][ODBC SQL Server Driver][SQL Server]DBCC failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER, ARITHABORT'.
Here are "all" the db options set for the DB
sp_dboption 'R1'
go
The following options are set:
-----------------------------------
torn page detection
auto create statistics
auto update statistics
Here is the explicit status of 'QUOTED_IDENTIFIER, ARITHABORT' settings:
OptionName                          CurrentSetting
----------------------------------- --------------
quoted identifier                   off
OptionName                          CurrentSetting
----------------------------------- --------------
arithabort                          off

Any clue why the 'QUOTED_IDENTIFIER, ARITHABORT' settings are not incorrect and what bearing does that have on the indexing job?

Viewing 6 posts - 1 through 5 (of 5 total)

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

iLoveSQL SSCrazy Points: 2888 More actions · Answer 1

Do you have computed columns in your table? You have to manually turn on the Quoted Identifier on if you do.

SET QUOTED_IDENTIFIER ON

DBCC DBREINDEX('

')

What exactly were you doing in the job?

Greg Charles SSC-Forever Points: 45403 More actions · Answer 2

This exact problem was addressed in another forum last week. See this Knowledgebase article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q301292

Greg

Le Rhun Philippe Say Hey Kid Points: 674 More actions · Answer 3

I have a similar problem in a full reindex job. Just try to put the arithabort and set quoted identifier on in your job and made à test . It will running well :

SET ARITHABORT ON

SET QUOTED_IDENTIFIER ON

Best regards

Joe Smith-187004 Newbie Points: 3 More actions · Answer 4

I have tried tried the above two settings, and all of these:

SET QUOTED_IDENTIFIER ON

SET ARITHABORT ON

SET ANSI_NULLS ON

SET ANSI_PADDING ON

SET ANSI_WARNINGS ON

SET CONCAT_NULL_YIELDS_NULL ON

SET NUMERIC_ROUNDABORT OFF

I still get the same error. I have looked at the KB article. Still failing. Any ideas?

Doug Blystone Ten Centuries Points: 1144 More actions · Answer 5

I too am havinga similiar problem but it is not a maintenance job.

I'm simply trying to delete rows from a table where a field is null. (the field is varchar(7000).

Please let me know if you have any suggestions.