Hugo Kornelis (2/15/2011)
The obvious solution would be to start using ANSI-compliant double quotes to delimit identifiers that need to be delimited.

Hugo Kornelis (2/15/2011)

---

I think the QUOTED_IDENTIFIER setting is to preserve backwards compatibility. With QUOTED_IDENTIFIER set to OFF, SQL Server reverts to its legacy behavior where both single and double quotes delimit strings, and only brackets delimit idenitifeers. With QUOTED_IDENTIFIER set to ON, we get the ANSI standard behavior where single quotes delimit strings and double quotes delimit identifiers, with the support for brackets as identifier delimiters kept in as a bonus. So you could get the third query to run without error message if you first SET QUOTED_IDENTIFIER OFF.

also heard that Microsoft should stop the usage of SET QUOTED_IDENTIFIER OFF while creating any objects.

Regards,
Hardik Doshi

SELECT * FROM sys.dm_os_performance_counters WHERE object_name LIKE ('%deprecated%')
 AND instance_name LIKE('%SET%')