1934: INSERT/UPDATE failed because the following SET options have incorrect settings
SQL ServerWhat 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.
More from this engine
- 5061ALTER DATABASE failed because a lock could not be placed on database
- 3702Cannot drop database because it is currently in use
- 15138The database principal owns a schema in the database, and cannot be dropped
- 468Cannot resolve the collation conflict
- 4864Bulk load data conversion error (type mismatch or invalid character)
- 916The server principal is not able to access the database under the current security context