Invalid column name

Here is my code. Very simple yet I'm getting "invalid column." I am using SQL Express.

FROM TemporaryCustomers
WHERE FirstName = "Cassady";

Try this:

  FROM TemporaryCustomers
 WHERE FirstName = 'Cassady'

I tried that and it worked with single quotes. What's weird is that I know I tried that before and it didn't work before so I don't know how to explain that.

Thank you for your suggestion.

To use double quote you must issue the following SET command first:


1 Like

True, but do yourself a favour and never ever set Quoted_Identifier to off. It's a legacy setting that causes all sorts of weirdness. Lots of newer functionality (and when I say newer I mean SQL 2005+) straight up just will not work unless Quoted_Indentifier is on.

Please enlighten us - which functionallity?

XQuery and XML data modification, Filtered Indexes, Indexed Views ….

1 Like

See Remarks under

try this


declare @myDoc xml  
set @myDoc = '<Root>  
<ProductDescription ProductID="1" ProductName="Road Bike">  
  <Warranty>1 year parts and labor</Warranty>  
  <Maintenance>3 year parts and labor extended maintenance is available</Maintenance>  
SELECT @myDoc.query('/Root/ProductDescription/Features')  

There are many situations where I have used SET QUOTED_IDENTIFIER OFF safely. As you point out, there are many situations where it can't be used. Awareness of which features require the ON setting are few enough to become familiar with. As with anything you do, ignorance can bite you if you don't study the effects of the settings you use. It isn't a legacy setting. It is supported in SQL Server 2017. You may be over stating the warning but it's good to become acquainted with it's usage and side effects.

  • Executing DDL on an index

  • Creating an indexed view or adding a computed column

    • These are the required settings for indexed views and computed columns: SET ANSI_NULLS, ANSI_PADDING, ANSI_WARNINGS, CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER ON; SET NUMERIC_ROUNDABORT OFF
  • Invoking XML data type methods

When I say legacy setting, I mean that it is a setting that exists purely to re-enable non-standard behaviour from old versions of SQL Server prior to the introduction of ANSI standards. There is no good reason to revert to that behaviour for newly developed code and it is only likely to cause you problems in future that you could have avoided by just using ANSI compliant behaviour originally. Note that some of these legacy behaviours, such as ANSI NULLS and CONCAT_NULL_YIELDS_NULL, are already flagged as being errors in a future SQL Server release and it's likely others will go that way at some point.

There is a reason I said "Do yourself a favour", it's less painful in the long run to just use the standards compliant method for quoting strings.