:::: MENU ::::

Posts Categorized / XML

  • Feb 14 / 2009
  • 0
dbDigger, XML

‘%.*ls’ is not a valid XML Index name because it starts with ‘%c’ character. XML Index name should not start with ‘#’ or ‘@’.

The error
‘%.*ls’ is not a valid XML Index name because it starts with ‘%c’ character. XML Index name should not start with ‘#’ or ‘@’.

is a run time error message of severity level 16. This error message appears when you try to create a XML index with an invalid name. The reason is that XML index names cannot start with the special characters ‘#’, and ‘@’. You must remove these characters from the start of the index name. This message is introduced in SQL Server 2005 and onwards.

  • Dec 19 / 2008
  • 0
dbDigger, XML

Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead.

The error message
Msg 3749, Level 16, State 1, Line 1
Cannot drop XML Index ‘%.*ls’ using old ‘Table.Index’ syntax, use ‘Index ON Table’ syntax instead.

is run time error message of severity level 16. This error message appears when you try to drop a XML index via the DROP INDEX tablename.indexname statement. To resolve the erro you should use the new DROP INDEX indexname ON tablename statement to drop a XML index.

  • Dec 17 / 2008
  • 0
Constraints and Keys, dbDigger, Indexes, XML

Cannot create primary xml index ‘%.*ls’ on ‘%.*ls’ because PRIMARY KEY constraint contains column(s) of type timestamp.

The error message
Msg 2735, Level 16, State 201, Line 1
Cannot create primary xml index ‘%.*ls’ on ‘%.*ls’ because PRIMARY KEY constraint contains column(s) of type timestamp.

is a run time error message of severity level 16. This error message appears when you try to create a XML index on a table for which the PRIMARY KEY constraint includes a column of the TIMESTAMP data type. To resolve the error make sure that the XML index is not created on the table as long as the PRIMARY KEY constraint contains the TIMESTAMP column.

Consult us to explore the Databases. Contact us