4

I have recently moved a database from Sql Server 2000 to Sql Server 2005. In the table designer, it insists on putting square brackets around a column named "Content" I don't see Content on the list of reserved words for Sql Server, so I don't understand why it is doing this. Is there a way I can prevent it?

pthalacker
  • 184
  • 1
  • 1
  • 9

3 Answers3

12

CONTENT is a keyword when defining an XML column with a schema.

See here.

Edit: The MSDN link is broken (per Champ's comment), so here is the relevant extract:

Creating a typed XML column is as simple as adding the name of the schema inside parentheses, as you see here:

CREATE TABLE Foo(FooID INT, someXml XML(CONTENT FooSchema))

This statement indicates that the someXml column must adhere to the XML Schema Collection named FooSchema. You can specify that the XML must be a document or that it can contain a fragment by including the appropriate keyword, DOCUMENT or CONTENT, respectively. If omitted, the default is CONTENT.

Community
  • 1
  • 1
Jeremy Smyth
  • 23,270
  • 2
  • 52
  • 65
  • 1
    all true tho they did forgot to add it to the list of reserved words on msdn :) anyway ... +1 nice link – Lil'Monkey Sep 04 '09 at 15:33
  • It is not in the list of keywords for sql server on MSDN – pthalacker Sep 18 '09 at 21:14
  • link is broken. Here is an archived content of the link: https://web.archive.org/web/20141006161826/http://msdn.microsoft.com/en-us/magazine/cc163611.aspx – Champ Apr 13 '16 at 22:04
3

The problem is that the field has the same name as the table. Sql Server 2000 did not seem to care about this potential ambiguity, but Sql Server 2005 does. When I add a field named Content to a table that is not named Content, the square brackets do not appear.

pamela

pthalacker
  • 184
  • 1
  • 1
  • 9
0

No, you can't prevent it. You can always add square brackets around a column name so it doesn't hurt anything.

David
  • 34,223
  • 3
  • 62
  • 80