Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 SQL Server Administration (2008)
 SQL Server Agent 'Jobs'

Author  Topic 

nhess80
Yak Posting Veteran

83 Posts

Posted - 2009-12-02 : 15:21:13
Im trying to schedule a Job to run some simple updates but when I try to test this out I keep getting the error below. I have searched all over and im unable to figure out my problem. Any help would be great. Thanks Nick

12/02/2009 14:18:59,Metro Billing,Error,0,CHICAGODB,Metro Billing,(Job outcome),,The job failed. The Job was invoked by User RSM. The last step to run was step 1 (Round Calls 6/6). The job was requested to start at step 1 (Round Calls 6/6).,00:00:00,0,0,,,,0


12/02/2009 14:18:59,Metro Billing,Error,1,CHICAGODB,Metro Billing,Round Calls 6/6,,Executed as user: NT AUTHORITY\NETWORK SERVICE. UPDATE failed because the following SET options have incorrect settings: 'QUOTED_IDENTIFIER'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. [SQLSTATE 42000] (Error 1934)Unable to open Step output file. The step failed.,00:00:00,16,1934,,,,0

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-12-02 : 15:37:50
You need to verify what's true in this part of the error message: "Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations." You can only run updates on these when the options are set properly.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page

nhess80
Yak Posting Veteran

83 Posts

Posted - 2009-12-02 : 16:12:33
Thats part of my problem. I don't know where to find these options. Can you point me in the right direction?

Thanks,
NIck


quote:
Originally posted by tkizer

You need to verify what's true in this part of the error message: "Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations." You can only run updates on these when the options are set properly.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."

Go to Top of Page

nhess80
Yak Posting Veteran

83 Posts

Posted - 2009-12-02 : 16:19:35
Also I have ran this query outside of the Job that was created and it always worked fine. Now that I created a job it has problems


Thats part of my problem. I don't know where to find these options. Can you point me in the right direction?

Thanks,
NIck

quote:
Originally posted by tkizer

You need to verify what's true in this part of the error message: "Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations." You can only run updates on these when the options are set properly.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."

Go to Top of Page

nhess80
Yak Posting Veteran

83 Posts

Posted - 2009-12-02 : 16:41:42
I figured it out. I need to put "SET QUOTED_IDENTIFIER ON " before I run the update query
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2009-12-02 : 18:30:37
It probably worked outside of the query because QUOTED_IDENTIFIER was on in your query window, but it's off in the job step. Glad you got it sorted out.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

"Let's begin with the premise that everything you've done up until this point is wrong."
Go to Top of Page
   

- Advertisement -