Comments on: SQL SERVER – QUOTED_IDENTIFIER ON/OFF and ANSI_NULL ON/OFF Explanation http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/ Notes of a SQL Server MVP and Database Administrator Sat, 21 Nov 2009 05:54:09 +0000 http://wordpress.com/ hourly 1 By: gemini twin http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-56427 gemini twin Mon, 05 Oct 2009 09:41:27 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-56427 SQL SERVER – QUOTED_IDENTIFIER ON/OFF and ANSI_NULL ON/OFF Explanation: i am using SQL server 2005 in affect to what is said about ANSI NULL ON and QUOTED IDENTIFIER ON, I do not get NULL if i place empty records in tables instead only an empty space appears please givme more details on these SQL SERVER – QUOTED_IDENTIFIER ON/OFF and ANSI_NULL ON/OFF Explanation:

i am using SQL server 2005
in affect to what is said about ANSI NULL ON and
QUOTED IDENTIFIER ON,
I do not get NULL if i place empty records in tables
instead only an empty space appears

please givme more details on these

]]> By: SQL SERVER - 2008 - Interview Questions and Answers - Part 4 Journey to SQL Authority with Pinal Dave http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-47467 SQL SERVER - 2008 - Interview Questions and Answers - Part 4 Journey to SQL Authority with Pinal Dave Thu, 26 Feb 2009 12:02:51 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-47467 [...] 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 cannot be quoted and must follow all Transact-SQL rules for identifiers. (Read More Here) [...] [...] 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 cannot be quoted and must follow all Transact-SQL rules for identifiers. (Read More Here) [...]

]]> By: SQLAuthority News - Best Articles on SQLAuthority.com Journey to SQL Authority with Pinal Dave http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-47184 SQLAuthority News - Best Articles on SQLAuthority.com Journey to SQL Authority with Pinal Dave Tue, 24 Feb 2009 12:06:51 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-47184 [...] SQL SERVER - QUOTED_IDENTIFIER ON/OFF and ANSI_NULL ON/OFF Explanation [...] [...] SQL SERVER – QUOTED_IDENTIFIER ON/OFF and ANSI_NULL ON/OFF Explanation [...]

]]> By: Jyothi P http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-42864 Jyothi P Tue, 16 Sep 2008 19:51:33 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-42864 When SET ANSI_NULLS is ON, all comparisons against a null value evaluate to UNKNOWN. (FALSE) When SET ANSI_NULLS is OFF, comparisons of all data against a null value evaluate to TRUE if the data value is NULL When SET ANSI_NULLS is ON, a SELECT statement using WHERE Emp_Name= NULL returns zero rows even if there are null values in Emp_Name. A SELECT statement using WHERE Emp_Name NULL returns zero rows even if there are nonnull values in Emp_Name. When SET ANSI_NULLS is OFF, the Equals (=) and Not Equal To () comparison operators do not follow the SQL-92 standard. A SELECT statement using WHERE Emp_Name= NULL returns the rows with null values Emp_Name. A SELECT statement using WHERE Emp_Name NULL returns the rows with nonnull values in the column. SET ANSI_NULLS also must be ON for executing distributed queries and when creating or manipulating indexes on computed columns or indexed views. If SET ANSI_NULLS is OFF, CREATE, UPDATE, INSERT, and DELETE statements on tables with indexes on computed columns or indexed views will fail. SQL Server will return an error listing all SET options violating the required values. When executing a SELECT statement, if SET ANSI_NULLS is OFF, SQL Server will ignore the index values on computed columns or views and resolve the select as though there were no such indexes on the tables or views. If you want a script to work regardless of the ANSI NULSS database option or the setting of SET ANSI_NULLS, use IS NULL and IS NOT NULL in comparisons that may contain null values. When SET ANSI_NULLS is ON, all comparisons against a null value evaluate to UNKNOWN. (FALSE)
When SET ANSI_NULLS is OFF, comparisons of all data against a null value evaluate to TRUE if the data value is NULL
When SET ANSI_NULLS is ON,

a SELECT statement using WHERE Emp_Name= NULL returns zero rows even if there are null values in Emp_Name.

A SELECT statement using WHERE Emp_Name NULL returns zero rows even if there are nonnull values in Emp_Name.

When SET ANSI_NULLS is OFF, the Equals (=) and Not Equal To () comparison operators do not follow the SQL-92 standard.

A SELECT statement using WHERE Emp_Name= NULL returns the rows with null values Emp_Name.

A SELECT statement using WHERE Emp_Name NULL returns the rows with nonnull values in the column.

SET ANSI_NULLS also must be ON for executing distributed queries and when creating or manipulating indexes on computed columns or indexed views.

If SET ANSI_NULLS is OFF, CREATE, UPDATE, INSERT, and DELETE statements on tables with indexes on computed columns or indexed views will fail. SQL Server will return an error listing all SET options violating the required values.

When executing a SELECT statement, if SET ANSI_NULLS is OFF, SQL Server will ignore the index values on computed columns or views and resolve the select as though there were no such indexes on the tables or views.

If you want a script to work regardless of the ANSI NULSS database option or the setting of SET ANSI_NULLS, use IS NULL and IS NOT NULL in comparisons that may contain null values.

]]> By: Harinath_hyd http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-33774 Harinath_hyd Fri, 15 Feb 2008 11:47:10 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-33774 Hi in a query set ansi_nulls on and select the null coulmn is gives null value if set ansi_nulls off also behave same. then how to know diff between the ansi_nulls on and off do mail to me. Thank you Hi
in a query set ansi_nulls on
and select the null coulmn is gives null value
if set ansi_nulls off also behave same.
then how to know diff between the ansi_nulls on and off
do mail to me.

Thank you

]]> By: Brian http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-18326 Brian Fri, 09 Nov 2007 16:11:11 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-18326 I'm a SQL beginner, and this stuff drives me crazy. However, we've using "is null" instead of "= null" and it seems to work regardless of the setting. Try this. This shows the difference between the two approaches: set ansi_nulls on declare @myTab table (id int null, [name] varchar(10) null) insert into @myTab (id,[name]) values (1, 'sam') insert into @myTab (id,[name]) values (2, 'dave') insert into @myTab (id,[name]) values (3, null) select * from @myTab select * from @myTab where [name] is null select * from @myTab where [name] = null I’m a SQL beginner, and this stuff drives me crazy. However, we’ve using “is null” instead of “= null” and it seems to work regardless of the setting. Try this. This shows the difference between the two approaches:

set ansi_nulls on

declare @myTab table (id int null, [name] varchar(10) null)

insert into @myTab (id,[name]) values (1, ’sam’)
insert into @myTab (id,[name]) values (2, ‘dave’)
insert into @myTab (id,[name]) values (3, null)

select * from @myTab
select * from @myTab where [name] is null
select * from @myTab where [name] = null

]]> By: Prashant Pandey http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-13045 Prashant Pandey Tue, 18 Sep 2007 00:37:06 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-13045 Got it... I have Created a table with fields Id and Name then i inserted many values in that table and also inserted a NULL value. in the Name field Then When i am rnning below querry it not returns any record to me. SET ANSI_NULLS ON SELECT Name FROM MyTable(Nolock) WHERE Name=NULL AND When iam running below querry it returns the row with NULL value SET ANSI_NULLS OFF SELECT Name FROM MyTable(Nolock) WHERE Name=NULL So, If in case of null when ANSI_NULLS is on Wht are the benefits of this i think this is wrong caz it does not return any row which having null. Why this is present in SQL any Specific reasons, Where we use this.???? Got it… I have Created a table with fields Id and Name then i inserted many values in that table and also inserted a NULL value. in the Name field
Then When i am rnning below querry it not returns any record to me.
SET ANSI_NULLS ON
SELECT Name FROM MyTable(Nolock) WHERE Name=NULL

AND
When iam running below querry it returns the row with NULL value
SET ANSI_NULLS OFF
SELECT Name FROM MyTable(Nolock) WHERE Name=NULL

So, If in case of null when ANSI_NULLS is on Wht are the benefits of this i think this is wrong caz it does not return any row which having null. Why this is present in SQL any Specific reasons, Where we use this.????

]]> By: Prashant Pandey http://blog.sqlauthority.com/2007/03/05/sql-server-quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-13042 Prashant Pandey Tue, 18 Sep 2007 00:22:25 +0000 http://blog.sqlauthority.com/2007/03/05/quoted_identifier-onoff-and-ansi_null-onoff-explanation/#comment-13042 Can u please provide any example of both of these, So that more clearly we can understand these. Can u please provide any example of both of these, So that more clearly we can understand these.

]]>