DBAtlas · Database operations atlas

1934: INSERT/UPDATE failed because the following SET options have incorrect settings

SQL Server

What does it mean?

A DML operation (INSERT/UPDATE/DELETE) failed because required SET options were set incorrectly. It typically occurs when the mandatory SET settings for indexed views, indexes on computed columns, filtered indexes or spatial/XML indexes are not met.

Why does it happen?

The affected table/view has an object that requires specific SET options (notably QUOTED_IDENTIFIER and ANSI_NULLS ON, NUMERIC_ROUNDABORT OFF, etc.), but the session's current SET options do not meet that requirement. Old client drivers or scripts that explicitly set wrong SET options trigger it.

How to fix it

Set the required options on the connection/session: SET QUOTED_IDENTIFIER ON; SET ANSI_NULLS ON; SET ANSI_PADDING ON; SET ANSI_WARNINGS ON; SET CONCAT_NULL_YIELDS_NULL ON; SET ARITHABORT ON; SET NUMERIC_ROUNDABORT OFF; Make sure the application driver sends these options correctly when connecting. The error message names the incorrect options; fix those.

Open in DBAtlas →

More from this engine