Error with simple INSERT statement

Question

I made an insert statement that runs inside a asp.net page. It gave me an error, so I went to the sql server and ran the statement as it should be and used it to compare with what I wrote in the asp.net page. The thing is, it it writen properly but it doesn't work. It can't seem to detect the database or the tables at all and tells me the table doesn't exist and neither do the colums. The statement looks like this:

INSERT [Remisiones].[dbo].[Places] (Name, Type) VALUES ("Planta 1", "Planta")

I have also tried using [dbo].[Places] and simply Places but it gives me an error at the place of the table saying it is an Invalid object name. What is it doing?

PS assuming the table is where you say it is, the error is probably Invalid column name... — Aaron Bertrand
– Aaron Bertrand, Commented Jun 24, 2012 at 16:27
I think you should've taken a look on sql server tsql basics before. — HichemSeeSharp
– HichemSeeSharp, Commented Jun 24, 2012 at 17:01

Aaron Bertrand · Accepted Answer · 2012-06-24 16:24:46Z

7

Don't use double quotes for string delimiters; use single quotes.

INSERT [Remisiones].[dbo].[Places] (Name, Type) VALUES ('Planta 1', 'Planta');

answered Jun 24, 2012 at 16:24

Aaron Bertrand

282k37 gold badges469 silver badges468 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

rdelfin Over a year ago

oh, ok. I was using mysql before and double quotes are accepted

user330315 Over a year ago

To spare you unpleasant surprises should you ever use a standard compliant database: Quoting using square brackets is non-standard and only understood by SQL Server (and probably Sybase as it shared the same roots). The SQL standard uses double quotes to quote object names which works in SQL Server as well. You might get yourself used to writing "Remissiones" instead of [Remisiones] - or even better avoid object names that need quoting alltogether.

Aaron Bertrand Over a year ago

@a_horse_with_no_name to clarify you are talking about delimiting objects and entities, not strings. While I understand the argument for double quotes as opposed to square brackets in the case of objects or entities, in SQL Server I always prefer to avoid double quotes in both cases. As you can see double quotes are often mistaken for valid string delimiters, and seeing them anywhere might give the wrong perception. (And these days there isn't a whole lot of code being written that will port directly to another RDBMS.)

user330315 Over a year ago

@AaronBertrand: absolutely. That's why I said "avoid object names that need quoting"

Aaron Bertrand Over a year ago

@a_horse_with_no_name I was merely clarifying because the question or answer wasn't talking about objects at all, just string literals. If someone just read the first two lines of your comment it might be confusing.

Collectives™ on Stack Overflow

Error with simple INSERT statement

1 Answer 1

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related