**We are self-hosted**
I have a job (created before my tenure at the organization) that is failing since I upgraded to 15.1.14 last night. There is one step in this job. The job history tells me that the "SET options have incorrect settings." Google told me that I need to to try SET QUOTED_IDENTIFIER ON;. However, all the examples I see involve store procs and my one step doesn't have a stored proc in it - it has this simple query:
update dbo.T_BATCH
set status = 'C',
close_dt = GETDATE(),
closed_by = created_by
where batch_type = 22 --internet batch type
and status in('O', 'H')
So ... if I just throw SET QUOTED_IDENTIFIER ON; before the query, will that fix my problem??? I don't know enough about QUOTED_IDENTIFIER to understand the impact.
Also, did something change with T_BATCH between v15.0 and v15.1?? I am trying to understand why an existing job, with such a simple query would break.
Ashley Elliott
Database Administrator
St. Louis Symphony Orchestra
314-286-4198
ashleye@slso.org
Geez! Nick from the helpdesk responded to my ticket in the time it took me to write this post!
In v15.1.8 a new index was added to the T_BATCH table, so updates to this table will now require a quoted identifier to be set.
Oh well! I hope this posted helps someone else someday.