SQL Server FAQs

Categories : Performance Tuning | DBA | Developer | Errors

XML parsing: line %d, character %d, unexpected end of input

Cannot create plan guide ‘%.ls’ because the statement specified by @stmt and @module_or_batch, or by @plan_handle and @statement_start_offset, matches the existing plan guide ‘%.ls’ in the database

Cannot %S_MSG %S_MSG ‘%.ls’ because it is referenced by plan guide ‘%.ls’. Use sp_control_plan_guide to drop the plan guide first. Record the plan guide definition for future use if needed.

XML parsing: line %d, character %d, end tag does not match start tag

Cannot create plan guide ‘%.ls’ because type ‘%.ls’ provided is not allowed.

Cannot create plan guide ‘%.*ls’ because its name is invalid. Plan guide name cannot begin with a ‘#’ character.

Cannot create %S_MSG on view “%.ls” because it references derived table “%.ls” (defined by SELECT statement in FROM clause). Consider removing the reference to the derived table or not indexing the view.

Cannot create plan guide ‘%.*ls’ because parameter @hints is incorrect. Use N’OPTION ( [ ,…n ] )’.

Cannot specify included columns for a clustered index.

Cannot create %S_MSG on view ‘%.*ls’ because it contains an INNER join that specifies a join hint. Consider removing the join hint.