SET ansi_nulls on ...

What does SET quoted_identifier on set ansi_nulls on  set quoted_identifier on go  mean?    syntax  set quoted_identifier {on | OFF}   Note   When SET QUOTED_IDENTIFIER is on, identifiers can be delimited by double quotation marks, and literals must be delimited by single quotation marks. When SET QUOTED_IDENTIFIER is OFF, identifiers are not quoted and must comply with all Transact-SQL identifier rules. For more information, see Using Identifiers. Text can be delimited by single or double quotation marks.    when SET quoted_identifier is on, all strings separated by double quotation marks are interpreted as object identifiers. Therefore, the quoted identifiers do not have to adhere to the Transact-SQL identifier rules. They can be reserved keywords and can contain characters that are not normally allowed in Transact-SQL identifiers. You cannot use double quotation marks to delimit literal string expressions, but you must enclose literal strings in single quotation marks. If the single quotation mark (') is part of a literal string, it can be represented by two single quotation marks ('). The SET quoted_identifier must be on when reserved keywords are used for object names in the database.    when SET QUOTED_IDENTIFIER is OFF (the default), the literal strings in the expression can be separated by either single or double quotation marks. If the literal string is delimited by double quotation marks, you can include embedded single quotation marks, such as ellipses, in the string.    SET QUOTED_IDENTIFIER must be on when an index is created or manipulated on a computed column or indexed view. If SET QUOTED_IDENTIFIER is OFF, the CREATE, UPDATE, INSERT, and DELETE statements on the indexed table on the computed column or indexed view will fail. What does  set ansi_nulls on mean? The &NBSP;&NBSP;SQL-92 standard requires that the value be FALSE when the null value equals (=) or does not equal (<>) is compared. When SET Ansi_nulls is on, the WHERE Colu is used even if the column_name contains null valuesMn_name = NULL The SELECT statement still returns 0 rows. SELECT statements that use WHERE column_name <> NULL will return 0 rows even if the column_name contains non-null values.    when SET ansi_nulls is OFF, the Equals (=) and non-equal (<>) comparison operators do not comply with the SQL-92 standard. Use the WHERE COLUMN_NAME = null SELECT statement to return rows that contain null values in column_name. Use the WHERE column_name <> NULL SELECT statement to return rows that contain non-null values in the column. Also, use the SELECT statement in WHERE column_name <> xyz_value to return all rows that are not xyz_value and not null.

SET ansi_nulls on ...