Error message sql server

@@ERROR (Transact-SQL)

Область применения: SQL Server (все поддерживаемые версии) База данных SQL Azure Управляемый экземпляр SQL Azure Azure Synapse Analytics Analytics Platform System (PDW)

Возвращает номер ошибки для последней выполненной инструкции Transact-SQL.

Соглашения о синтаксисе Transact-SQL

Синтаксис

Ссылки на описание синтаксиса Transact-SQL для SQL Server 2014 и более ранних версий, см. в статье Документация по предыдущим версиям.

Типы возвращаемых данных

Примечания

Возвращает 0, если в предыдущей инструкции Transact-SQL не возникло ошибок.

Возвращает номер ошибки, если в предыдущей инструкции возникла ошибка. Если ошибка относится к представлению каталога sys.messages, @@ERROR содержит значение столбца sys.messages.message_id для этой ошибки. Можно просмотреть текст, связанный с номером ошибки @@ERROR в sys.messages.

Поскольку функция @@ERROR очищается и сбрасывается для каждой выполняемой инструкции, проверяйте ее сразу после инструкции или сохраните значение в локальную переменную для последующей проверки.

Для обработки ошибок используйте конструкцию TRY. CATCH. Конструкция TRY. CATCH также поддерживает дополнительные системные функции (ERROR_LINE, ERROR_MESSAGE, ERROR_PROCEDURE, ERROR_SEVERITY и ERROR_STATE), возвращающие более подробные сведения, чем @@ERROR. Кроме того, TRY. CATCH поддерживает функцию ERROR_NUMBER, которая не ограничена тем, что возвращает номер ошибки немедленно после выполнения инструкции. Дополнительные сведения см. в разделе TRY. CATCH (Transact-SQL).

Примеры

A. Использование функции @@ERROR для обнаружения конкретной ошибки

В следующем примере функция @@ERROR используется для проверки проверочного ограничения (ошибка 547) в инструкции UPDATE .

Б. Использование функции @@ERROR для выхода из процедуры по условию

В приведенном ниже примере инструкции IF. ELSE выполняют проверку @@ERROR после инструкции DELETE в хранимой процедуре. Значение переменной @@ERROR определяет код возврата, который отправляется вызывающей программе и указывает на успешное или неуспешное выполнение процедуры.

В. Использование функции @@ERROR с @@ROWCOUNT

В следующем примере инструкция @@ERROR с @@ROWCOUNT используется для проверки операции инструкции UPDATE . Значение @@ERROR проверяется на ошибки, а @@ROWCOUNT обеспечивает успешное применение обновления к строке таблицы.

Источник

ERROR_MESSAGE (Transact-SQL)

Область применения: SQL Server (все поддерживаемые версии) База данных SQL Azure Управляемый экземпляр SQL Azure Azure Synapse Analytics Analytics Platform System (PDW)

Эта функция возвращает текст сообщения об ошибке, которая вызвала выполнение блока CATCH конструкции TRY. CATCH.

Соглашения о синтаксисе Transact-SQL

Синтаксис

Ссылки на описание синтаксиса Transact-SQL для SQL Server 2014 и более ранних версий, см. в статье Документация по предыдущим версиям.

Типы возвращаемых данных

nvarchar(4000)

Возвращаемое значение

При вызове в блоке CATCH функция ERROR_MESSAGE возвращает полный текст сообщения об ошибке, запустившей блок CATCH . Текст содержит значения подставляемых параметров, таких как длина, имена объектов или время.

Функция ERROR_MESSAGE возвращает значение NULL в случае вызова вне блока CATCH.

Функцию ERROR_MESSAGE можно вызывать в любом месте области действия блока CATCH.

Функция ERROR_MESSAGE возвращает соответствующее сообщение об ошибке независимо от количества ее выполнений или от места ее вызова в области действия блока CATCH . В этом ее отличие от таких функций, как @@ERROR, которые возвращают номер ошибки только в той инструкции, которая непосредственно следует за инструкцией, вызвавшей ошибку.

Во вложенных блоках CATCH функция ERROR_MESSAGE возвращает сообщение об ошибке, соответствующее области действия блока CATCH , который ссылался на данный блок CATCH . Например, блок CATCH внешней конструкции TRY. CATCH может содержать внутреннюю конструкцию TRY. CATCH . Во внутреннем блоке CATCH функция ERROR_MESSAGE возвращает сообщение об ошибке, вызвавшей внутренний блок CATCH . Если функция ERROR_MESSAGE выполняется во внешнем блоке CATCH , она возвращает сообщение об ошибке, вызвавшей внешний блок CATCH .

Примеры

A. Использование функции ERROR_MESSAGE в блоке CATCH

В приведенном ниже примере показана инструкция SELECT , вызывающая ошибку деления на ноль. Блок CATCH возвращает сообщение об ошибке.

Б. Использование функции ERROR_MESSAGE в блоке CATCH с другими средствами обработки ошибок

В приведенном ниже примере показана инструкция SELECT , вызывающая ошибку деления на ноль. Вместе с сообщением об ошибке блок CATCH возвращает сведения о ней.

Источник

ERROR_MESSAGE (Transact-SQL)

Applies to: SQL Server (all supported versions) Azure SQL Database Azure SQL Managed Instance Azure Synapse Analytics Analytics Platform System (PDW)

This function returns the message text of the error that caused the CATCH block of a TRY. CATCH construct to execute.

Transact-SQL syntax conventions

Syntax

To view Transact-SQL syntax for SQL Server 2014 and earlier, see Previous versions documentation.

Return Types

nvarchar(4000)

Return Value

When called in a CATCH block, ERROR_MESSAGE returns the complete text of the error message that caused the CATCH block to run. The text includes the values supplied for any substitutable parameters — for example, lengths, object names, or times.

ERROR_MESSAGE returns NULL when called outside the scope of a CATCH block.

ERROR_MESSAGE supports calls anywhere within the scope of a CATCH block.

ERROR_MESSAGE returns a relevant error message regardless of how many times it runs, or where it runs within the scope of the CATCH block. This contrasts with a function like @@ERROR, which only returns an error number in the statement immediately following the one that causes an error.

In nested CATCH blocks, ERROR_MESSAGE returns the error message specific to the scope of the CATCH block that referenced that CATCH block. For example, the CATCH block of an outer TRY. CATCH construct could have an inner TRY. CATCH construct. Inside that inner CATCH block, ERROR_MESSAGE returns the message from the error that invoked the inner CATCH block. If ERROR_MESSAGE runs in the outer CATCH block, it returns the message from the error that invoked that outer CATCH block.

Examples

A. Using ERROR_MESSAGE in a CATCH block

This example shows a SELECT statement that generates a divide-by-zero error. The CATCH block returns the error message.

Here is the result set.

B. Using ERROR_MESSAGE in a CATCH block with other error-handling tools

This example shows a SELECT statement that generates a divide-by-zero error. Along with the error message, the CATCH block returns information about that error.

Источник

[Перевод] Обработка ошибок и транзакций в SQL Server. Часть 1. Обработка ошибок – быстрый старт

Привет, Хабр! Представляю вашему вниманию перевод статьи «Error and Transaction Handling in SQL Server. Part One – Jumpstart Error Handling» автора Erland Sommarskog.

1. Введение

Эта статья – первая в серии из трёх статей, посвященных обработке ошибок и транзакций в SQL Server. Её цель – дать вам быстрый старт в теме обработки ошибок, показав базовый пример, который подходит для большей части вашего кода. Эта часть написана в расчете на неопытного читателя, и по этой причине я намеренно умалчиваю о многих деталях. В данный момент задача состоит в том, чтобы рассказать как без упора на почему. Если вы принимаете мои слова на веру, вы можете прочесть только эту часть и отложить остальные две для дальнейших этапов в вашей карьере.

С другой стороны, если вы ставите под сомнение мои рекомендации, вам определенно необходимо прочитать две остальные части, где я погружаюсь в детали намного более глубоко, исследуя очень запутанный мир обработки ошибок и транзакций в SQL Server. Вторая и третья части, так же, как и три приложения, предназначены для читателей с более глубоким опытом. Первая статья — короткая, вторая и третья значительно длиннее.

Все статьи описывают обработку ошибок и транзакций в SQL Server для версии 2005 и более поздних версий.

1.1 Зачем нужна обработка ошибок?

Почему мы обрабатываем ошибки в нашем коде? На это есть много причин. Например, на формах в приложении мы проверяем введенные данные и информируем пользователей о допущенных при вводе ошибках. Ошибки пользователя – это предвиденные ошибки. Но нам также нужно обрабатывать непредвиденные ошибки. То есть, ошибки могут возникнуть из-за того, что мы что-то упустили при написании кода. Простой подход – это прервать выполнение или хотя бы вернуться на этап, в котором мы имеем полный контроль над происходящим. Недостаточно будет просто подчеркнуть, что совершенно непозволительно игнорировать непредвиденные ошибки. Это недостаток, который может вызвать губительные последствия: например, стать причиной того, что приложение будет предоставлять некорректную информацию пользователю или, что еще хуже, сохранять некорректные данные в базе. Также важно сообщать о возникновении ошибки с той целью, чтобы пользователь не думал о том, что операция прошла успешно, в то время как ваш код на самом деле ничего не выполнил.

Мы часто хотим, чтобы в базе данных изменения были атомарными. Например, задача по переводу денег с одного счета на другой. С этой целью мы должны изменить две записи в таблице CashHoldings и добавить две записи в таблицу Transactions. Абсолютно недопустимо, чтобы ошибки или сбой привели к тому, что деньги будут переведены на счет получателя, а со счета отправителя они не будут списаны. По этой причине обработка ошибок также касается и обработки транзакций. В приведенном примере нам нужно обернуть операцию в BEGIN TRANSACTION и COMMIT TRANSACTION, но не только это: в случае ошибки мы должны убедиться, что транзакция откачена.

2. Основные команды

Мы начнем с обзора наиболее важных команд, которые необходимы для обработки ошибок. Во второй части я опишу все команды, относящиеся к обработке ошибок и транзакций.

2.1 TRY-CATCH

Основным механизмом обработки ошибок является конструкция TRY-CATCH, очень напоминающая подобные конструкции в других языках. Структура такова:

Если какая-либо ошибка появится в , выполнение будет переведено в блок CATCH, и будет выполнен код обработки ошибок.

Как правило, в CATCH откатывают любую открытую транзакцию и повторно вызывают ошибку. Таким образом, вызывающая клиентская программа понимает, что что-то пошло не так. Повторный вызов ошибки мы обсудим позже в этой статье.

Вот очень быстрый пример:

Результат выполнения: This is the error: Divide by zero error encountered.

Мы вернемся к функции error_message() позднее. Стоит отметить, что использование PRINT в обработчике CATCH приводится только в рамках экспериментов и не следует делать так в коде реального приложения.

Если вызывает хранимую процедуру или запускает триггеры, то любая ошибка, которая в них возникнет, передаст выполнение в блок CATCH. Если более точно, то, когда возникает ошибка, SQL Server раскручивает стек до тех пор, пока не найдёт обработчик CATCH. И если такого обработчика нет, SQL Server отправляет сообщение об ошибке напрямую клиенту.

Есть одно очень важное ограничение у конструкции TRY-CATCH, которое нужно знать: она не ловит ошибки компиляции, которые возникают в той же области видимости. Рассмотрим пример:

Как можно видеть, блок TRY присутствует, но при возникновении ошибки выполнение не передается блоку CATCH, как это ожидалось. Это применимо ко всем ошибкам компиляции, таким как пропуск колонок, некорректные псевдонимы и тому подобное, которые возникают во время выполнения. (Ошибки компиляции могут возникнуть в SQL Server во время выполнения из-за отложенного разрешения имен – особенность, благодаря которой SQL Server позволяет создать процедуру, которая обращается к несуществующим таблицам.)

Эти ошибки не являются полностью неуловимыми; вы не можете поймать их в области, в которой они возникают, но вы можете поймать их во внешней области. Добавим такой код к предыдущему примеру:

Теперь мы получим на выходе это:

На этот раз ошибка была перехвачена, потому что сработал внешний обработчик CATCH.

2.2 SET XACT_ABORT ON

В начало ваших хранимых процедур следует всегда добавлять это выражение:

Оно активирует два параметра сессии, которые выключены по умолчанию в целях совместимости с предыдущими версиями, но опыт доказывает, что лучший подход – это иметь эти параметры всегда включенными. Поведение SQL Server по умолчанию в той ситуации, когда не используется TRY-CATCH, заключается в том, что некоторые ошибки прерывают выполнение и откатывают любые открытые транзакции, в то время как с другими ошибками выполнение последующих инструкций продолжается. Когда вы включаете XACT_ABORT ON, почти все ошибки начинают вызывать одинаковый эффект: любая открытая транзакция откатывается, и выполнение кода прерывается. Есть несколько исключений, среди которых наиболее заметным является выражение RAISERROR.

Параметр XACT_ABORT необходим для более надежной обработки ошибок и транзакций. В частности, при настройках по умолчанию есть несколько ситуаций, когда выполнение может быть прервано без какого-либо отката транзакции, даже если у вас есть TRY-CATCH. Мы видели такой пример в предыдущем разделе, где мы выяснили, что TRY-CATCH не перехватывает ошибки компиляции, возникшие в той же области. Открытая транзакция, которая не была откачена из-за ошибки, может вызвать серьезные проблемы, если приложение работает дальше без завершения транзакции или ее отката.

Для надежной обработки ошибок в SQL Server вам необходимы как TRY-CATCH, так и SET XACT_ABORT ON. Среди них инструкция SET XACT_ABORT ON наиболее важна. Если для кода на промышленной среде только на нее полагаться не стоит, то для быстрых и простых решений она вполне подходит.

Параметр NOCOUNT не имеет к обработке ошибок никакого отношения, но включение его в код является хорошей практикой. NOCOUNT подавляет сообщения вида (1 row(s) affected), которые вы можете видеть в панели Message в SQL Server Management Studio. В то время как эти сообщения могут быть полезны при работе c SSMS, они могут негативно повлиять на производительность в приложении, так как увеличивают сетевой трафик. Сообщение о количестве строк также может привести к ошибке в плохо написанных клиентских приложениях, которые могут подумать, что это данные, которые вернул запрос.

Выше я использовал синтаксис, который немного необычен. Большинство людей написали бы два отдельных выражения:

Между ними нет никакого отличия. Я предпочитаю версию с SET и запятой, т.к. это снижает уровень шума в коде. Поскольку эти выражения должны появляться во всех ваших хранимых процедурах, они должны занимать как можно меньше места.

3. Основной пример обработки ошибок

После того, как мы посмотрели на TRY-CATCH и SET XACT_ABORT ON, давайте соединим их вместе в примере, который мы можем использовать во всех наших хранимых процедурах. Для начала я покажу пример, в котором ошибка генерируется в простой форме, а в следующем разделе я рассмотрю решения получше.

Для примера я буду использовать эту простую таблицу.

Вот хранимая процедура, которая демонстрирует, как вы должны работать с ошибками и транзакциями.

Первая строка в процедуре включает XACT_ABORT и NOCOUNT в одном выражении, как я показывал выше. Эта строка – единственная перед BEGIN TRY. Все остальное в процедуре должно располагаться после BEGIN TRY: объявление переменных, создание временных таблиц, табличных переменных, всё. Даже если у вас есть другие SET-команды в процедуре (хотя причины для этого встречаются редко), они должны идти после BEGIN TRY.

Причина, по которой я предпочитаю указывать SET XACT_ABORT и NOCOUNT перед BEGIN TRY, заключается в том, что я рассматриваю это как одну строку шума: она всегда должна быть там, но я не хочу, чтобы это мешало взгляду. Конечно же, это дело вкуса, и если вы предпочитаете ставить SET-команды после BEGIN TRY, ничего страшного. Важно то, что вам не следует ставить что-либо другое перед BEGIN TRY.

Часть между BEGIN TRY и END TRY является основной составляющей процедуры. Поскольку я хотел использовать транзакцию, определенную пользователем, я ввел довольно надуманное бизнес-правило, в котором говорится, что если вы вставляете пару, то обратная пара также должна быть вставлена. Два выражения INSERT находятся внутри BEGIN и COMMIT TRANSACTION. Во многих случаях у вас будет много строк кода между BEGIN TRY и BEGIN TRANSACTION. Иногда у вас также будет код между COMMIT TRANSACTION и END TRY, хотя обычно это только финальный SELECT, возвращающий данные или присваивающий значения выходным параметрам. Если ваша процедура не выполняет каких-либо изменений или имеет только одно выражение INSERT/UPDATE/DELETE/MERGE, то обычно вам вообще не нужно явно указывать транзакцию.

В то время как блок TRY будет выглядеть по-разному от процедуры к процедуре, блок CATCH должен быть более или менее результатом копирования и вставки. То есть вы делаете что-то короткое и простое и затем используете повсюду, не особо задумываясь. Обработчик CATCH, приведенный выше, выполняет три действия:

1. Откатывает любые открытые транзакции.
2. Повторно вызывает ошибку.
3. Убеждается, что возвращаемое процедурой значение отлично от нуля.

Эти три действия должны всегда быть там. Мы можете возразить, что строка

не нужна, если нет явной транзакции в процедуре, но это абсолютно неверно. Возможно, вы вызываете хранимую процедуру, которая открывает транзакцию, но которая не может ее откатить из-за ограничений TRY-CATCH. Возможно, вы или кто-то другой добавите явную транзакцию через два года. Вспомните ли вы тогда о том, что нужно добавить строку с откатом? Не рассчитывайте на это. Я также слышу читателей, которые возражают, что если тот, кто вызывает процедуру, открыл транзакцию, мы не должны ее откатывать… Нет, мы должны, и если вы хотите знать почему, вам нужно прочитать вторую и третью части. Откат транзакции в обработчике CATCH – это категорический императив, у которого нет исключений.

Код повторной генерации ошибки включает такую строку:

Встроенная функция error_message() возвращает текст возникшей ошибки. В следующей строке ошибка повторно вызывается с помощью выражения RAISERROR. Это не самый простой способ вызова ошибки, но он работает. Другие способы мы рассмотрим в следующей главе.

Замечание: синтаксис для присвоения начального значения переменной в DECLARE был внедрен в SQL Server 2008. Если у вас SQL Server 2005, вам нужно разбить строку на DECLARE и выражение SELECT.

Финальное выражение RETURN – это страховка. RAISERROR никогда не прерывает выполнение, поэтому выполнение следующего выражения будет продолжено. Пока все процедуры используют TRY-CATCH, а также весь клиентский код обрабатывает исключения, нет повода для беспокойства. Но ваша процедура может быть вызвана из старого кода, написанного до SQL Server 2005 и до внедрения TRY-CATCH. В те времена лучшее, что мы могли делать, это смотреть на возвращаемые значения. То, что вы возвращаете с помощью RETURN, не имеет особого значения, если это не нулевое значение (ноль обычно обозначает успешное завершение работы).

Последнее выражение в процедуре – это END CATCH. Никогда не следует помещать какой-либо код после END CATCH. Кто-нибудь, читающий процедуру, может не увидеть этот кусок кода.

После прочтения теории давайте попробуем тестовый пример:

Давайте добавим внешнюю процедуру для того, чтобы увидеть, что происходит при повторном вызове ошибки:

Мы получили корректное сообщение об ошибке, но если вы посмотрите на заголовки этого сообщения и на предыдущее поближе, то можете заметить проблему:

Сообщение об ошибке выводит информацию о расположении конечного выражения RAISERROR. В первом случае некорректен только номер строки. Во втором случае некорректно также имя процедуры. Для простых процедур, таких как наш тестовый пример, это не является большой проблемой. Но если у вас есть несколько уровней вложенных сложных процедур, то наличие сообщения об ошибке с отсутствием указания на место её возникновения сделает поиск и устранение ошибки намного более сложным делом. По этой причине желательно генерировать ошибку таким образом, чтобы можно было определить нахождение ошибочного фрагмента кода быстро, и это то, что мы рассмотрим в следующей главе.

4. Три способа генерации ошибки

4.1 Использование error_handler_sp

Мы рассмотрели функцию error_message(), которая возвращает текст сообщения об ошибке. Сообщение об ошибке состоит из нескольких компонентов, и существует своя функция error_xxx() для каждого из них. Мы можем использовать их для повторной генерации полного сообщения, которое содержит оригинальную информацию, хотя и в другом формате. Если делать это в каждом обработчике CATCH, это будет большой недостаток — дублирование кода. Вам не обязательно находиться в блоке CATCH для вызова error_message() и других подобных функций, и они вернут ту же самую информацию, если будут вызваны из хранимой процедуры, которую выполнит блок CATCH.

Позвольте представить вам error_handler_sp:

Первое из того, что делает error_handler_sp – это сохраняет значение всех error_xxx() функций в локальные переменные. Я вернусь к выражению IF через секунду. Вместо него давайте посмотрим на выражение SELECT внутри IF:

Цель этого SELECT заключается в форматировании сообщения об ошибке, которое передается в RAISERROR. Оно включает в себя всю информацию из оригинального сообщения об ошибке, которое мы не можем вставить напрямую в RAISERROR. Мы должны обработать имя процедуры, которое может быть NULL для ошибок в обычных скриптах или в динамическом SQL. Поэтому используется функция COALESCE. (Если вы не понимаете форму выражения RAISERROR, я рассказываю о нем более детально во второй части.)

Отформатированное сообщение об ошибке начинается с трех звездочек. Этим достигаются две цели: 1) Мы можем сразу видеть, что это сообщение вызвано из обработчика CATCH. 2) Это дает возможность для error_handler_sp отфильтровать ошибки, которые уже были сгенерированы один или более раз, с помощью условия NOT LIKE ‘***%’ для того, чтобы избежать изменения сообщения во второй раз.

Вот как обработчик CATCH должен выглядеть, когда вы используете error_handler_sp:

Давайте попробуем несколько тестовых сценариев.

Заголовки сообщений говорят о том, что ошибка возникла в процедуре error_handler_sp, но текст сообщений об ошибках дает нам настоящее местонахождение ошибки – как название процедуры, так и номер строки.

Я покажу еще два метода вызова ошибок. Однако error_handler_sp является моей главной рекомендацией для читателей, которые читают эту часть. Это — простой вариант, который работает на всех версиях SQL Server начиная с 2005. Существует только один недостаток: в некоторых случаях SQL Server генерирует два сообщения об ошибках, но функции error_xxx() возвращают только одну из них, и поэтому одно из сообщений теряется. Это может быть неудобно при работе с административными командами наподобие BACKUPRESTORE, но проблема редко возникает в коде, предназначенном чисто для приложений.

4.2. Использование ;THROW

В SQL Server 2012 Microsoft представил выражение ;THROW для более легкой обработки ошибок. К сожалению, Microsoft сделал серьезную ошибку при проектировании этой команды и создал опасную ловушку.

С выражением ;THROW вам не нужно никаких хранимых процедур. Ваш обработчик CATCH становится таким же простым, как этот:

Достоинство ;THROW в том, что сообщение об ошибке генерируется точно таким же, как и оригинальное сообщение. Если изначально было два сообщения об ошибках, оба сообщения воспроизводятся, что делает это выражение еще привлекательнее. Как и со всеми другими сообщениями об ошибках, ошибки, сгенерированные ;THROW, могут быть перехвачены внешним обработчиком CATCH и воспроизведены. Если обработчика CATCH нет, выполнение прерывается, поэтому оператор RETURN в данном случае оказывается не нужным. (Я все еще рекомендую оставлять его, на случай, если вы измените свое отношение к ;THROW позже).

Если у вас SQL Server 2012 или более поздняя версия, измените определение insert_data и outer_sp и попробуйте выполнить тесты еще раз. Результат в этот раз будет такой:

Имя процедуры и номер строки верны и нет никакого другого имени процедуры, которое может нас запутать. Также сохранены оригинальные номера ошибок.

В этом месте вы можете сказать себе: действительно ли Microsoft назвал команду ;THROW? Разве это не просто THROW? На самом деле, если вы посмотрите в Books Online, там не будет точки с запятой. Но точка с запятой должны быть. Официально они отделяют предыдущее выражение, но это опционально, и далеко не все используют точку с запятой в выражениях T-SQL. Более важно, что если вы пропустите точку с запятой перед THROW, то не будет никакой синтаксической ошибки. Но это повлияет на поведение при выполнении выражения, и это поведение будет непостижимым для непосвященных. При наличии активной транзакции вы получите сообщение об ошибке, которое будет полностью отличаться от оригинального. И еще хуже, что при отсутствии активной транзакции ошибка будет тихо выведена без обработки. Такая вещь, как пропуск точки с запятой, не должно иметь таких абсурдных последствий. Для уменьшения риска такого поведения, всегда думайте о команде как о ;THROW (с точкой с запятой).

Нельзя отрицать того, что ;THROW имеет свои преимущества, но точка с запятой не единственная ловушка этой команды. Если вы хотите использовать ее, я призываю вас прочитать по крайней мере вторую часть этой серии, где я раскрываю больше деталей о команде ;THROW. До этого момента, используйте error_handler_sp.

4.3. Использование SqlEventLog

Третий способ обработки ошибок – это использование SqlEventLog, который я описываю очень детально в третьей части. Здесь я лишь сделаю короткий обзор.

SqlEventLog предоставляет хранимую процедуру slog.catchhandler_sp, которая работает так же, как и error_handler_sp: она использует функции error_xxx() для сбора информации и выводит сообщение об ошибке, сохраняя всю информацию о ней. Вдобавок к этому, она логирует ошибку в таблицу splog.sqleventlog. В зависимости от типа приложения, которое у вас есть, эта таблица может быть очень ценным объектом.

Для использования SqlEventLog, ваш обработчик CATCH должен быть таким:

@@procid возвращает идентификатор объекта текущей хранимой процедуры. Это то, что SqlEventLog использует для логирования информации в таблицу. Используя те же тестовые сценарии, получим результат их работы с использованием catchhandler_sp:

Как вы видите, сообщение об ошибке отформатировано немного не так, как это делает error_handler_sp, но основная идея такая же. Вот образец того, что было записано в таблицу slog.sqleventlog:

logid	logdate	errno	severity	logproc	linenum	msgtext
1	2015-01-25 22:40:24.393	515	16	insert_data	5	Cannot insert .
2	2015-01-25 22:40:24.395	2627	14	insert_data	6	Violation of .

Если вы хотите попробовать SqlEventLog, вы можете загрузить файл sqleventlog.zip. Инструкция по установке находится в третьей части, раздел Установка SqlEventLog.

5. Финальные замечания

Вы изучили основной образец для обработки ошибок и транзакций в хранимых процедурах. Он не идеален, но он должен работать в 90-95% вашего кода. Есть несколько ограничений, на которые стоит обратить внимание:

1. Как мы видели, ошибки компиляции не могут быть перехвачены в той же процедуре, в которой они возникли, а только во внешней процедуре.
2. Пример не работает с пользовательскими функциями, так как ни TRY-CATCH, ни RAISERROR нельзя в них использовать.
3. Когда хранимая процедура на Linked Server вызывает ошибку, эта ошибка может миновать обработчик в хранимой процедуре на локальном сервере и отправиться напрямую клиенту.
4. Когда процедура вызвана как INSERT-EXEC, вы получите неприятную ошибку, потому что ROLLBACK TRANSACTION не допускается в данном случае.
5. Как упомянуто выше, если вы используете error_handler_sp или SqlEventLog, мы потеряете одно сообщение, когда SQL Server выдаст два сообщения для одной ошибки. При использовании ;THROW такой проблемы нет.

Я рассказываю об этих ситуациях более подробно в других статьях этой серии.

Перед тем как закончить, я хочу кратко коснуться триггеров и клиентского кода.

Триггеры

Пример для обработки ошибок в триггерах не сильно отличается от того, что используется в хранимых процедурах, за исключением одной маленькой детали: вы не должны использовать выражение RETURN (потому что RETURN не допускается использовать в триггерах).

С триггерами важно понимать, что они являются частью команды, которая запустила триггер, и в триггере вы находитесь внутри транзакции, даже если не используете BEGIN TRANSACTION.
Иногда я вижу на форумах людей, которые спрашивают, могут ли они написать триггер, который не откатывает в случае падения запустившую его команду. Ответ таков: нет способа сделать это надежно, поэтому не стоит даже пытаться. Если в этом есть необходимость, по возможности не следует использовать триггер вообще, а найти другое решение. Во второй и третьей частях я рассматриваю обработку ошибок в триггерах более подробно.

Клиентский код

У вас должна быть обработка ошибок в коде клиента, если он имеет доступ к базе. То есть вы должны всегда предполагать, что при любом вызове что-то может пойти не так. Как именно внедрить обработку ошибок, зависит от конкретной среды.

Здесь я только обращу внимание на важную вещь: реакцией на ошибку, возвращенную SQL Server, должно быть завершение запроса во избежание открытых бесхозных транзакций:

Это также применимо к знаменитому сообщению Timeout expired (которое является не сообщением от SQL Server, а от API).

6. Конец первой части

Это конец первой из трех частей серии. Если вы хотели изучить вопрос обработки ошибок быстро, вы можете закончить чтение здесь. Если вы настроены идти дальше, вам следует прочитать вторую часть, где наше путешествие по запутанным джунглям обработки ошибок и транзакций в SQL Server начинается по-настоящему.

… и не забывайте добавлять эту строку в начало ваших хранимых процедур:

Источник

Error	Severity	Description
1	10	Version date of last upgrade: 10/11/90.
21	10	Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator.
53	10	An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 — Could not open a connection to SQL Server ) (.Net SqlClient Data Provider).
101	15	Query not allowed in Waitfor.
102	15	Incorrect syntax near ‘%.*ls’.
103	15	The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d.
104	15	ORDER BY items must appear in the select list if the statement contains a UNION operator.
105	15	Unclosed quotation mark before the character string ‘%.*ls’.
106	16	Too many table names in the query. The maximum allowable is %d.
107	15	The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query.
108	15	The ORDER BY position number is out of range of the number of items in the select list.
109	15	There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
110	15	There are fewer columns in the INSERT statement than values specified in the VALUES clause.  The number of values in the VALUES clause must match the number of columns specified in the INSERT statement.
111	15	‘CREATE FUNCTION’ must be the first statement in a query batch.
112	15	Variables are not allowed in the %ls statement.
113	15	Missing end comment mark ‘*/’.
114	15	Browse mode is invalid for a statement that assigns values to a variable.
115	15	The FOR UPDATE clause is invalid for statements containing set operators.
116	15	Only one expression can be specified in the select list when the subquery is not introduced with EXISTS.
117	15	The object name «Object Name» contains more than the maximum number of prefixes.  The maximum is 2.
118	15	Only members of the sysadmin role can specify the %ls option for the %ls statement.
119	15	Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’.
120	15	The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns.
121	15	The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns.
122	15	The %ls option is allowed only with %ls syntax.
123	15	Batch/procedure exceeds maximum length of %d characters.
124	15	CREATE PROCEDURE contains no statements.
125	15	Case expressions may only be nested to level %d.
126	15	Invalid pseudocolumn «%.*ls».
127	15	A TOP N value may not be negative.
128	15	The name ‘<Column Name>’ is not permitted in this context. Only constants, expressions, or variables allowed here. Column names are not permitted.
129	15	Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100.
130	16	Cannot perform an aggregate function on an expression containing an aggregate or a subquery.
131	15	The size (<Data Type Size>) given to the type ‘varchar / char / nvarchar / nchar / binary / varbinary’ exceeds the maximum allowed for any data type (8000). The size (<Data Type Size>) given to the column ‘<Column Name>’ exceeds the maximum allowed for any data type (8000).
132	15	The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure.
133	15	A GOTO statement references the label ‘<Label Name>’ but the label has not been declared.
134	15	The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure.
135	15	Cannot use a BREAK statement outside the scope of a WHILE statement.
136	15	Cannot use a CONTINUE statement outside the scope of a WHILE statement.
137	15	Must declare the scalar variable ‘<Variable Name>’.
138	15	Correlation clause in a subquery not permitted.
139	15	Cannot assign a default value to a local variable.
140	15	Can only use IF UPDATE within a CREATE TRIGGER statement.
141	15	A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations.
142	15	Incorrect syntax for definition of the ‘%ls’ constraint.
143	15	A COMPUTE BY item was not found in the order by list. All expressions in the compute by list must also be present in the order by list.
144	15	Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause.
145	15	ORDER BY items must appear in the select list if SELECT DISTINCT is specified.
146	15	Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded.
147	15	An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference.
148	15	Incorrect time syntax in time string ‘<Wait Time>’ used with WAITFOR.
149	15	Time value ‘%.*ls’ used with WAITFOR is not a valid value. Check date/time syntax.
150	15	Both terms of an outer join must contain columns.
151	15	‘%.*ls’ is an invalid money value.
152	15	The same large data placement option «%.*ls» has been specified twice.
153	15	Invalid usage of the option %.*ls in the %ls statement.
154	15	a COMPUTE clause is not allowed in a SELECT INTO statement.
155	15	‘<DATEADD option>’ is not a recognized DATEADD option.
156	15	Incorrect syntax near the keyword ‘%.*ls’.
157	15	An aggregate may not appear in the set list of an UPDATE statement.
158	15	An aggregate may not appear in the OUTPUT clause.
159	15	SQL Server 2005, SQL Server 2008 — Must specify the table name and index name for the DROP INDEX statement. SQL Server 2000 — For DROP INDEX, you must give both the table and the index name, in the form tablename.indexname.
160	15	Rule does not contain a variable.
161	15	Rule contains more than one variable.
162	15	Invalid expression in the TOP clause.
163	15	The compute by list does not match the order by list.
164	15	Each GROUP BY expression must contain at least one column that is not an outer reference. GROUP BY expressions must refer to column names that appear in the select list.
165	16	Privilege %ls may not be granted or revoked.
166	15	‘CREATE VIEW’ does not allow specifying the database name as a prefix to the object name.
167	16	Cannot create a trigger on a temporary object.
168	15	The %S_MSG ‘%.*ls’ is out of the range of computer representation (%d bytes).
169	15	A column has been specified more than once in the order by list. Columns in the order by list must be unique.
170	15	Line %d: Incorrect syntax near ‘%.*ls’.
171	15	Cannot use SELECT INTO in browse mode.
172	15	Cannot use HOLDLOCK in browse mode.
173	15	The definition for column <Column Name> must include a data type.
174	15	The dateadd function requires 3 arguments.
175	15	An aggregate may not appear in a computed column expression or check constraint.
176	15	The FOR BROWSE clause is no longer supported in views. Set the database compatibility level to 80 or lower for this statement to be allowed.
177	15	The IDENTITY function can only be used when the SELECT statement has an INTO clause.
178	15	A RETURN statement with a return value cannot be used in this context.
179	15	Cannot use the OUTPUT option when passing a constant to a stored procedure.
180	15	There are too many parameters in this %ls statement. The maximum number is %d.
181	15	SQL Server 2008 — Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. SQL Server 2005 — Cannot use the OUTPUT option in a DECLARE or CREATE FUNCTION statement. SQL Server 2000 — Cannot use the OUTPUT option in a DECLARE statement.
182	15	Table and column names must be supplied for the READTEXT or WRITETEXT utility.
183	15	The scale (<Scale Value>) for column ‘<Column Name>’ must be within the range 0 to <Precision Value>.
184	15	DEFAULT cannot be specified more than once for filegroups of the same content type.
185	15	Data stream is invalid for WRITETEXT statement in bulk form.
186	15	Data stream missing from WRITETEXT statement.
187	16	The valid range for MAX_QUEUE_READERS is 0 to 32767.
188	15	Cannot specify a log device in a CREATE DATABASE statement without also specifying at least one non-log device.
189	15	The %ls function requires %d to %d arguments.
190	15	An invalid date or time was specified in the statement.
191	15	Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.
192	16	The scale must be less than or equal to the precision.
193	15	The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters.
194	15	A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable.
195	15	‘Function Name’ is not a recognized function name.
196	15	SELECT INTO must be the first query in an SQL statement containing a UNION, INTERSECT or EXCEPT operator.
197	15	EXECUTE cannot be used as a source when inserting into a table variable.
198	15	Browse mode is invalid for statements containing a UNION operator.
199	15	An INSERT statement cannot contain a SELECT statement that assigns values to a variable.
201	16	Procedure ‘<Procedure Name>’ expects parameter ‘<Parameter Name>’, which was not supplied.
202	16	Invalid type ‘%s’ for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types.
203	16	The name ‘%.*ls’ is not a valid identifier.
204	20	Normalization error in node %ls.
205	16	All queries in an SQL statement containing a UNION operator must have an equal number of expressions in their target lists.
206	16	Operand type clash: %ls is incompatible with %ls
207	16	Invalid column name ‘%.*ls’.
208	16	Invalid object name ‘%.*ls’.
209	16	Ambiguous column name ‘%.*ls’.
210	16	Syntax error converting datetime from binary/varbinary string.
211	12	SyntaxPossible schema corruption. Run DBCC CHECKCATALOG.
212	16	Expression result length exceeds the maximum. %d max, %d found.
213	16	Insert Error: Column name or number of supplied values does not match table definition.
214	16	Procedure expects parameter ‘%ls’ of type ‘%ls’.
215	16	Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.
216	16	Parameters were not supplied for the function ‘%.*ls’.
217	16	Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d).
218	16	Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission.
219	16	The type ‘%.*ls’ already exists, or you do not have permission to create it.
220	16	Arithmetic overflow error for data type %ls, value = %ld.
221	10	FIPS Warning: Implicit conversion from %ls to %ls.
222	16	The base type «%.*ls» is not a valid base type for the alias data type.
223	11	Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default.
224	11	Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default.
225	16	The parameters supplied for the %ls «%.*ls» are not valid.
226	16	%ls statement not allowed within multi-statement transaction.
227	15	%.*ls is not a valid function, property, or field.
228	15	Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value.
229	14	%ls permission denied on object ‘%.*ls’, database ‘%.*ls’, owner ‘%.*ls’.
230	14	%ls permission denied on column ‘%.*ls’ of object ‘%.*ls’, database ‘%.*ls’, owner ‘%.*ls’.
231	11	No such default. ID = %ld, database ID = %d.
232	16	Arithmetic overflow error for type %ls, value = %f.
233	16	The column ‘%.*ls’ in table ‘%.*ls’ cannot be null.
234	16	There is insufficient result space to convert a money value to varchar / nvarchar / char / nchar.
235	16	Cannot convert a char value to money. The char value has incorrect syntax.
236	16	The conversion from char data type to money resulted in a money overflow error.
237	16	There is insufficient result space to convert a money value to int / smallint / tinyint.
238	16	There is insufficient result space to convert the %ls value (= %d) to the money data type.
239	16	Duplicate common table expression name ‘%.*ls’ was specified.
240	16	Types don’t match between the anchor and the recursive part in column «<Column Name>» of recursive query «<Recursive CTE>».
241	16	Syntax error converting datetime from character string.
242	16	The conversion of a char data type to a datetime data type resulted in an out-of-range datetime value.
243	16	Type <Data Type> is not a defined system type.
244	16	The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column.
245	16	Syntax error converting the varchar value to a column of data type int.
246	16	No anchor member was specified for recursive query «%.*ls».
247	16	An anchor member was found in the recursive part of recursive query «%.*ls».
248	16	The conversion of the %ls value ‘%.*ls’ overflowed an int column. Maximum integer value exceeded.
249	16	The type «%ls» is not comparable. It cannot be used in the %ls clause.

Error	Severity	Description
251	16	Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded.
252	16	Recursive common table expression ‘<Common Table Expression Name>’ does not contain a top-level UNION ALL operator.
253	16	Recursive member of a common table expression ‘<Common Table Expression Name>’ has multiple recursive references.
254	16	Prefixed columns are not allowed in the column list of a PIVOT operator.
255	16	Pseudocolumns are not allowed in the column list of a PIVOT operator.
256	16	The data type int is invalid for the substring function.  Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary.
257	16	Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query.
258	16	Cannot call methods on %ls.
259	16	Ad hoc updates to system catalogs are not enabled. The system administrator must reconfigure SQL Server to allow this.
260	16	Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query.
261	16	‘%.*ls’ is not a recognized function.
262	16	%ls permission denied in database ‘%.*ls’.
263	16	Must specify table to select from.
264	16	Column name ‘%.*ls’ appears more than once in the result column list.
265	16	The column name «%.*ls» specified in the %ls operator conflicts with the existing column name in the %ls argument.
266	16	Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = %ld, current count = %ld.
267	16	Object ‘%.*ls’ cannot be found.
268	16	Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option.
270	16	Object ‘%.*ls’ cannot be modified.
271	16	SQL Server 2005, SQL Server 2008, SQL Server 2012 — The column ‘<Column Name>’ cannot be modified because it is either a computed column or is the result of a UNION operator. SQL Server 2000 — Column ‘<Column Name>’ cannot be modified because it is a computed column.
272	16	Cannot update a timestamp column.
273	16	Cannot insert a non-null value into a timestamp column. Use INSERT with a column list or with a default of NULL for the timestamp column.
275	16	Prefixes are not allowed in value or pivot columns of an UNPIVOT operator.
276	16	Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator.
277	16	The column «%.*ls» is specified multiple times in the column list of the UNPIVOT operator.
278	16	The text, ntext, and image data types cannot be used in a GROUP BY clause.
279	16	The text, ntext, and image data types are invalid in this subquery or aggregate expression.
280	16	Only text, ntext, and image columns are valid with the TEXTPTR function.
281	16	<Style number> is not a valid style number when converting from %ls to a character string.
282	10	The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead.
283	16	READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger.
284	16	Rules cannot be bound to text, ntext, or image data types.
285	16	The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions.
286	16	The logical tables INSERTED and DELETED cannot be updated.
287	16	The %ls statement is not allowed within a trigger.
288	16	The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only.
290	16	Invalid EXECUTE statement using object «%ls», method «%ls».
291	16	CAST or CONVERT: invalid attributes specified for type ‘%.*ls’
292	16	There is insufficient result space to convert a smallmoney value to varchar/nvarchar.
293	16	Cannot convert char value to smallmoney. The char value has incorrect syntax.
294	16	The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error.
295	16	Syntax error converting character string to smalldatetime data type.
296	16	The conversion of char data type to smalldatetime data type resulted in an out-of-range smalldatetime value.
297	16	The user does not have permission to perform this action.
298	16	The conversion from datetime data type to smalldatetime data type resulted in a smalldatetime overflow error.
299	16	The DATEADD function was called with bad type %ls.
300	14	%ls permission was denied on object ‘%.*ls’, database ‘%.*ls’.
301	16	Query contains an outer-join request that is not permitted.
302	16	The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type ‘uniqueidentifier’ in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression.
303	16	The table ‘%.*ls’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause.
304	16	‘%d’ is out of range for index option ‘%.*ls’. See sp_configure option ‘%ls’ for valid values.
305	16	The XML data type cannot be compared or sorted, except when using the IS NULL operator.
306	16	The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator.
307	16	Index ID %d on table ‘%.*ls’ (specified in the FROM clause) does not exist.
308	16	Index ‘%.*ls’ on table ‘%.*ls’ (specified in the FROM clause) does not exist.
309	16	Cannot use index «%.*ls» on table «%.*ls» in a hint. XML indexes are not allowed in hints.
310	16	The value <MAXRECURSION value> specified for the MAXRECURSION option exceeds the allowed maximum of %d.
311	16	Cannot use text, ntext, or image columns in the ‘inserted’ and ‘deleted’ tables.
312	16	Cannot reference text, ntext, or image columns in a filter stored procedure.
313	16	An insufficient number of arguments were supplied for the procedure or function %.*ls.
314	16	Cannot use GROUP BY ALL with the special tables INSERTED or DELETED.
315	16	Index «%.*ls» on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
316	16	The index ID %d on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online.
317	16	Table-valued function ‘<Function Name>’ cannot have a column alias.
318	16	The table (and its columns) returned by a table-valued method need to be aliased.
319	16	Incorrect syntax near the keyword ‘with’. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon.
320	16	The compile-time variable value for ‘%.*ls’ in the OPTIMIZE FOR clause must be a literal.
321	15	%.*ls is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90.
322	16	The variable «%.*ls» is specified in the OPTIMIZE FOR clause, but is not used in the query.
323	16	The ‘COMPUTE’ clause is not allowed in a statement containing an INTERSECT or EXCEPT operator.
324	15	The ‘ALL’ version of the %.*ls operator is not supported.
325	15	Incorrect syntax near ‘%.*ls’. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE.
326	16	Multi-part identifier ‘%.*ls’ is ambiguous. Both columns ‘%.*ls’ and ‘%.*ls’ exist.
327	16	Function call ‘%.*ls’ is ambiguous: both a user-defined function and a method call with this name exist.
328	16	A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables.
329	16	Each GROUP BY expression must contain at least one column reference.
330	15	The target ‘<Object Name>’ of the OUTPUT INTO clause cannot be a view or common table expression.
331	15	The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot have any enabled triggers.
332	15	The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint ‘<Primary Key or Foreign Key Constraint Name>’.
333	15	The target table ‘<Table Name>’ of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule ‘<CHECK Constraint Name>’.
334	15	The target table ‘<Table Name>’ of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause.
335	16	Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ‘%.*ls’ without parameters instead.
336	15	Incorrect syntax near ‘%.*ls’. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon.
337	10	Warning: the floating point value ‘%.*ls’ is too small. It will be interpreted as 0.
338	16	READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers.
339	16	DEFAULT or NULL are not allowed as explicit identity values.
340	16	Cannot create the trigger «%.*ls» on view «%.*ls». AFTER triggers cannot be created on views.
341	16	Replication filter procedures may not contain columns of large object, large value, XML or CLR type.
342	16	Column «%.*ls» is not allowed in this context, and the user-defined function or aggregate «%.*ls» could not be found.
343	16	Unknown object type ‘%.*ls’ used in a CREATE, DROP, or ALTER statement.
344	16	Remote function reference ‘%.*ls’ is not allowed, and the column name ‘%.*ls’ could not be found or is ambiguous.
345	16	Function ‘%.*ls’ is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound.
346	15	The parameter «<Parameter Name>» can not be declared READONLY since it is not a table-valued parameter.
347	16	The table-valued parameter «%.*ls» cannot be declared as an OUTPUT parameter.
348	16	The table variable «%.*ls» can not be passed to a stored procedure with the OUTPUT option.
349	16	The procedure «%.*ls» has no parameter named «%.*ls».
350	16	The column «%.*ls» does not have a valid data type. A column cannot be of a user-defined table type.
351	16	Column, parameter, or variable %.*ls. : Cannot find data type %.*ls.
352	15	The table-valued parameter «%.*ls» must be declared with the READONLY option.
353	16	Function ‘%.*ls’ is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound.
354	15	The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
355	15	The target table ‘<Table Name>’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement.
356	15	The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’.
357	15	The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule ‘%ls’.
358	15	The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules. Found rule ‘%ls’.
359	15	The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used.
360	15	The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both.
361	16	The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns.
362	16	The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘<Object Name>’ did not match the key column names of the index ‘<Index Name>’.
363	16	The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ cannot be used with the %S_MSG specified by index ‘%.*ls’.
364	16	The query processor could not produce a query plan because the FORCESEEK hint on view ‘<View Name>’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view.
365	16	The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ specified more seek columns than the number of key columns in index ‘%.*ls’.
366	16	The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘<Object Name>’ cannot be used with the column store index ‘%.*ls’.
401	16	Unimplemented statement or expression %ls.
402	16	The data types %s and %s are incompatible in the %s operator.
403	16	Invalid operator for data type. Operator equals add, type equals text.
404	16	The column reference «inserted.%.*ls» is not allowed because it refers to a base table that is not being modified in this statement.
405	16	A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement.
406	16	%ls cannot be used in the PIVOT operator because it is not invariant to NULLs.
407	16	Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x.
408	16	A constant expression was encountered in the ORDER BY list, position %i.
409	16	The %ls operation cannot take a %ls data type as an argument.
410	20	COMPUTE clause #%d ‘BY’ expression #%d is not in the order by list.
411	16	COMPUTE clause #%d, aggregate expression #%d is not in the select list.
412	16	The column «%.*ls» is not updatable because it is derived or constant.
413	16	Correlated parameters or sub-queries are not supported by the inline function «%.*ls».
414	16	UPDATE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF UPDATE trigger.
415	16	DELETE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF DELETE trigger.
416	16	The service queue «%.*ls» cannot be directly updated.
417	16	TOP is not allowed in an UPDATE or DELETE statement against a partitioned view.
418	16	Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object ‘%.*ls’.
420	16	The text, ntext, and image data types cannot be used in an ORDER BY clause.
421	16	The text/ntext/image data type cannot be selected as DISTINCT because it is not comparable.
422	16	Common table expression defined but not used.
423	16	Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls».
424	16	Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement.
425	16	Data type %ls of receiving variable is not equal to the data type %ls of column ‘%.*ls’.
426	16	The length %d of the receiving variable is less than the length %d of the column ‘%.*ls’.
427	20	Could not load sysprocedures entries for constraint ID %d in database ID %d.
428	20	Could not find row in sysconstraints for constraint ID %d in database ID %d.
429	20	Could not find new constraint ID %d in sysconstraints, database ID %d, at compile time.
430	20	Could not resolve table name for object ID %d, database ID %d, when compiling foreign key.
431	19	Could not bind foreign key constraint. Too many tables involved in the query.
432	16	Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls».
433	20	Could not find CHECK constraint for ‘%.*ls’, although the table is flagged as having one.
434	16	Function ‘%ls’ is not allowed in the OUTPUT clause.
435	16	Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement.
436	20	Could not open referenced table ID %d in database ID %d.
437	20	Could not resolve the referenced column name in table ID %d.
438	20	Could not resolve the referencing column name in table ID %d.
439	20	Could not find FOREIGN KEY constraints for table ‘%.*ls’ in database ID %d although the table is flagged as having them.
440	16	Internal query compilation error. The stack overflow could not be handled.
441	16	Cannot use the ‘%ls’ function on a remote data source.
442	16	The NEST argument must be a column reference. Expressions are not allowed.
443	16	Invalid use of ‘getdate’ within a function. Invalid use of ‘INSERT’ within a function. Invalid use of ‘UPDATE’ within a function.
444	16	Select statements included within a function cannot return data to a client.
445	16	COLLATE clause cannot be used on expressions containing a COLLATE clause.
446	16	Cannot resolve collation conflict for %ls operation.
447	16	Expression type %ls is invalid for COLLATE clause.
448	16	Invalid collation ‘%.*ls’.
449	16	Collation conflict caused by collate clauses with different collation ‘%.*ls’ and ‘%.*ls’.
450	16	Code page translations are not supported for the text data type. From: %d To: %d.
451	16	Cannot resolve collation conflict for column %d in %ls statement.
452	16	COLLATE clause cannot be used on user-defined data types.
453	16	Collation ‘%.*ls’ is supported on Unicode data types only and cannot be set at the database or server level.
454	16	The UNNEST argument must be a nested table column.
455	16	The last statement included within a function must be a return statement.
456	16	Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict.
457	16	Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict.
458	16	Cannot create the SELECT INTO target table «%.*ls» because the xml column «%.*ls» is typed with a schema collection «%.*ls» from database «%.*ls». Xml columns cannot refer to schemata across databases.
459	16	Collation ‘%.*ls’ is supported on Unicode data types only and cannot be applied to char, varchar or text data types.
460	16	DISTINCT operator is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’.
461	16	TOP operator is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’.
462	16	Outer join is not allowed in the recursive part of a recursive common table expression ‘<Common Table Expression Name>’.
463	16	Functions with parameters are not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
464	16	Functions with side effects are not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
465	16	Recursive references are not allowed in subqueries.
466	16	UNION operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’.
467	16	GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression ‘<CTE Name>’.
468	16	Cannot resolve the collation conflict between «%.*ls» and «%.*ls» in the %ls operation.
469	16	An explicit column list must be specified for target table ‘%.*ls’ when table hint KEEPIDENTITY is used and the table contains an identity column.
470	16	The synonym «<Synonym Name>» referenced synonym «<Synonym Name>». Synonym chaining is not allowed.
471	16	Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified.
472	16	Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified.
473	16	The incorrect value «%.*ls» is supplied in the PIVOT operator.
474	16	Unable to load the computed column definitions for table «%.*ls».
475	16	Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled.
476	16	Invalid PERCENT tablesample size «<sample_number>» for table «<Table Name>». The PERCENT tablesample size must be between 0 and 100.
477	16	Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table «<Table Name>». The value or seed must be an integer.
478	16	The TABLESAMPLE clause cannot be used in a view definition or inline table function definition.
479	16	Invalid ROWS value or REPEATABLE seed «%I64d» in the TABLESAMPLE clause for table «%.*ls». The value or seed must be greater than 0.
480	16	The TABLESAMPLE clause cannot be used with the table function «%.*ls».
481	16	The TABLESAMPLE clause cannot be used with the linked server table «%.*ls».
482	16	Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause.
483	16	The OUTPUT clause cannot be used in an INSERT…EXEC statement.
484	16	Cannot declare more than %d local variables.
485	16	Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column «%.*ls» is typed with the schema collection «%.*ls», which is registered in database «%.*ls».
486	16	%.*ls does not allow specifying a schema name as a prefix to the assembly name.
487	16	An invalid option was specified for the statement «%.*ls».
488	16	%s columns must be comparable. The type of column «%.*ls» is «%s», which is not comparable.
489	16	The OUTPUT clause cannot be specified because the target view «%.*ls» is a partitioned view.
490	16	The resync functionality is temporarily disabled.
491	16	A correlation name must be specified for the bulk rowset in the from clause.
492	16	Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name «%.*ls» is a duplicate.
493	16	The column ‘%.*ls’ that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks.
494	16	The TABLESAMPLE clause can only be used with local tables.
495	16	The return table column «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
496	16	The parameter «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata.
497	16	Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses.
498	16	Invalid value in the TABLESAMPLE or the REPEATABLE clause.
499	16	Invalid parameter for the getchecksum function.
500	16	Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s).

message_id severity is_event_logged text 21 20 0 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. 101 15 0 Query not allowed in Waitfor. 102 15 0 Incorrect syntax near ‘%.*ls’. 103 15 0 The %S_MSG that starts with ‘%.*ls’ is too long. Maximum length is %d. 104 15 0 ORDER BY items must appear in the select list if the statement contains a UNION, INTERSECT or EXCEPT operator. 105 15 0 Unclosed quotation mark after the character string ‘%.*ls’. 106 16 0 Too many table names in the query. The maximum allowable is %d. 107 15 0 The column prefix ‘%.*ls’ does not match with a table name or alias name used in the query. 108 15 0 The ORDER BY position number %ld is out of range of the number of items in the select list. 109 15 0 There are more columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 110 15 0 There are fewer columns in the INSERT statement than values specified in the VALUES clause. The number of values in the VALUES clause must match the number of columns specified in the INSERT statement. 111 15 0 ‘%ls’ must be the first statement in a query batch. 112 15 0 Variables are not allowed in the %ls statement. 113 15 0 Missing end comment mark ‘*/’. 114 15 0 Browse mode is invalid for a statement that assigns values to a variable. 115 15 0 The FOR UPDATE clause is invalid for statements containing set operators. 116 15 0 Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. 117 15 0 The %S_MSG name ‘%.*ls’ contains more than the maximum number of prefixes. The maximum is %d. 119 15 0 Must pass parameter number %d and subsequent parameters as ‘@name = value’. After the form ‘@name = value’ has been used, all subsequent parameters must be passed in the form ‘@name = value’. 120 15 0 The select list for the INSERT statement contains fewer items than the insert list. The number of SELECT values must match the number of INSERT columns. 121 15 0 The select list for the INSERT statement contains more items than the insert list. The number of SELECT values must match the number of INSERT columns. 122 15 0 The %ls option is allowed only with %ls syntax. 123 15 0 Batch/procedure exceeds maximum length of %d characters. 124 15 0 CREATE PROCEDURE contains no statements. 125 15 0 Case expressions may only be nested to level %d. 126 15 0 Invalid pseudocolumn «%.*ls». 127 15 0 A TOP N or FETCH rowcount value may not be negative. 128 15 0 The name «%.*s» is not permitted in this context. Valid expressions are constants, constant expressions, and (in some contexts) variables. Column names are not permitted. 129 15 0 Fillfactor %d is not a valid percentage; fillfactor must be between 1 and 100. 130 16 0 Cannot perform an aggregate function on an expression containing an aggregate or a subquery. 131 15 0 The size (%d) given to the %S_MSG ‘%.*ls’ exceeds the maximum allowed for any data type (%d). 132 15 0 The label ‘%.*ls’ has already been declared. Label names must be unique within a query batch or stored procedure. 133 15 0 A GOTO statement references the label ‘%.*ls’ but the label has not been declared. 134 15 0 The variable name ‘%.*ls’ has already been declared. Variable names must be unique within a query batch or stored procedure. 135 15 0 Cannot use a BREAK statement outside the scope of a WHILE statement. 136 15 0 Cannot use a CONTINUE statement outside the scope of a WHILE statement. 137 15 0 Must declare the scalar variable «%.*ls». 138 15 0 Correlation clause in a subquery not permitted. 139 15 0 Cannot assign a default value to a local variable. 140 15 0 Can only use IF UPDATE within a CREATE TRIGGER statement. 141 15 0 A SELECT statement that assigns a value to a variable must not be combined with data-retrieval operations. 142 15 0 Incorrect syntax for definition of the ‘%ls’ constraint. 144 15 0 Cannot use an aggregate or a subquery in an expression used for the group by list of a GROUP BY clause. 145 15 0 ORDER BY items must appear in the select list if SELECT DISTINCT is specified. 146 15 0 Could not allocate ancillary table for a subquery. Maximum number of tables in a query (%d) exceeded. 147 15 0 An aggregate may not appear in the WHERE clause unless it is in a subquery contained in a HAVING clause or a select list, and the column being aggregated is an outer reference. 148 15 0 Incorrect time syntax in time string ‘%.*ls’ used with WAITFOR. 149 15 0 Time value ‘%.*ls’ used with WAITFOR is not a valid value. Check date/time syntax. 150 15 0 Time value %d used with MAX_DURATION is not a valid value; MAX_DURATION wait time must be greater or equal to 0 and less or equal to %d. 151 15 0 ‘%.*ls’ is an invalid money value. 152 15 0 The same large data placement option «%.*ls» has been specified twice. 153 15 0 Invalid usage of the option %.*ls in the %ls statement. 154 15 0 %S_MSG is not allowed in %S_MSG. 155 15 0 ‘%.*ls’ is not a recognized %ls option. 156 15 0 Incorrect syntax near the keyword ‘%.*ls’. 157 15 0 An aggregate may not appear in the set list of an UPDATE statement. 158 15 0 An aggregate may not appear in the OUTPUT clause. 159 15 0 Must specify the table name and index name for the DROP INDEX statement. 160 15 0 Rule does not contain a variable. 161 15 0 Rule contains more than one variable. 162 15 0 Invalid expression in a TOP or OFFSET clause. 164 15 0 Each GROUP BY expression must contain at least one column that is not an outer reference. 165 16 0 Privilege %ls may not be granted or revoked. 166 15 0 ‘%ls’ does not allow specifying the database name as a prefix to the object name. 167 15 0 Cannot create %S_MSG on a temporary object. 168 15 0 The floating point value ‘%.*ls’ is out of the range of computer representation (%d bytes). 169 15 0 A column has been specified more than once in the order by list. Columns in the order by list must be unique. 171 15 0 Browse mode cannot be used with INSERT, SELECT INTO, or UPDATE statements. 172 15 0 Cannot use HOLDLOCK in browse mode. 173 15 0 The definition for column ‘%.*ls’ must include a data type. 174 15 0 The %.*ls function requires %d argument(s). 175 15 0 An aggregate may not appear in a computed column expression or check constraint. 176 15 0 The FOR BROWSE clause is no longer supported in views. 177 15 0 The IDENTITY function can only be used when the SELECT statement has an INTO clause. 178 15 0 A RETURN statement with a return value cannot be used in this context. 179 15 0 Cannot use the OUTPUT option when passing a constant to a stored procedure. 180 15 0 There are too many parameters in this %ls statement. The maximum number is %d. 181 15 0 Cannot use the OUTPUT option in a DECLARE, CREATE AGGREGATE or CREATE FUNCTION statement. 182 15 0 Table and column names must be supplied for the READTEXT or WRITETEXT utility. 183 15 0 The scale (%d) for column ‘%.*ls’ must be within the range %d to %d. 184 16 0 DEFAULT cannot be specified more than once for filegroups of the same content type. 185 15 0 Data stream is invalid for WRITETEXT statement in bulk form. 186 15 0 Data stream missing from WRITETEXT statement. 187 16 0 The valid range for MAX_QUEUE_READERS is 0 to 32767. 188 15 0 Cannot specify a log file in a CREATE DATABASE statement without also specifying at least one data file. 189 15 0 The %ls function requires %d to %d arguments. 190 15 0 An invalid date or time was specified in the statement. 191 15 0 Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries. 192 16 0 The scale must be less than or equal to the precision. 193 15 0 The object or column name starting with ‘%.*ls’ is too long. The maximum length is %d characters. 194 15 0 A SELECT INTO statement cannot contain a SELECT statement that assigns values to a variable. 195 15 0 ‘%.*ls’ is not a recognized %S_MSG. 196 15 0 SELECT INTO must be the first query in a statement containing a UNION, INTERSECT or EXCEPT operator. 197 15 0 EXECUTE cannot be used as a source when inserting into a table variable. 198 15 0 Browse mode is invalid for statements containing a UNION, INTERSECT or EXCEPT operator. 199 15 0 An INSERT statement cannot contain a SELECT statement that assigns values to a variable. 201 16 0 Procedure or function ‘%.*ls’ expects parameter ‘%.*ls’, which was not supplied. 202 16 0 Invalid type ‘%s’ for WAITFOR. Supported data types are CHAR/VARCHAR, NCHAR/NVARCHAR, and DATETIME. WAITFOR DELAY supports the INT and SMALLINT data types. 203 16 0 The name ‘%.*ls’ is not a valid identifier. 204 20 1 Normalization error in node %ls. 205 16 0 All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists. 206 16 0 Operand type clash: %ls is incompatible with %ls 207 16 0 Invalid column name ‘%.*ls’. 208 16 0 Invalid object name ‘%.*ls’. 209 16 0 Ambiguous column name ‘%.*ls’. 210 16 0 Conversion failed when converting datetime from binary/varbinary string. 211 23 1 Corruption in database ID %I64d, object ID %ld possibly due to schema or catalog inconsistency. Run DBCC CHECKCATALOG. 212 16 0 Expression result length exceeds the maximum. %d max, %d found. 213 16 0 Column name or number of supplied values does not match table definition. 214 16 0 Procedure expects parameter ‘%ls’ of type ‘%ls’. 215 16 0 Parameters supplied for object ‘%.*ls’ which is not a function. If the parameters are intended as a table hint, a WITH keyword is required. 216 16 0 Parameters were not supplied for the function ‘%.*ls’. 217 16 0 Maximum stored procedure, function, trigger, or view nesting level exceeded (limit %d). 218 16 0 Could not find the type ‘%.*ls’. Either it does not exist or you do not have the necessary permission. 219 16 0 The type ‘%.*ls’ already exists, or you do not have permission to create it. 220 16 0 Arithmetic overflow error for data type %ls, value = %ld. 221 10 0 FIPS Warning: Implicit conversion from %ls to %ls. 222 16 0 The base type «%.*ls» is not a valid base type for the alias data type. 223 11 0 Object ID %ld specified as a default for table ID %ld, column ID %d is missing or not of type default. 224 11 0 Object ID %ld specified as a rule for table ID %ld, column ID %d is missing or not of type default. 225 16 0 The parameters supplied for the %ls «%.*ls» are not valid. 226 16 0 %ls statement not allowed within multi-statement transaction. 227 15 0 «%.*ls» is not a valid function, property, or field. 228 15 0 Method ‘%.*ls’ of type ‘%.*ls’ in assembly ‘%.*ls’ does not return any value. 229 14 0 The %ls permission was denied on the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’. 230 14 0 The %ls permission was denied on the column ‘%.*ls’ of the object ‘%.*ls’, database ‘%.*ls’, schema ‘%.*ls’. 231 11 0 No such default. ID = %ld, database ID = %d. 232 16 0 Arithmetic overflow error for type %ls, value = %f. 233 16 0 The column ‘%.*ls’ in table ‘%.*ls’ cannot be null. 234 16 0 There is insufficient result space to convert a money value to %ls. 235 16 0 Cannot convert a char value to money. The char value has incorrect syntax. 236 16 0 The conversion from char data type to money resulted in a money overflow error. 237 16 0 There is insufficient result space to convert a money value to %ls. 239 16 0 Duplicate common table expression name ‘%.*ls’ was specified. 240 16 0 Types don’t match between the anchor and the recursive part in column «%.*ls» of recursive query «%.*ls». 241 16 0 Conversion failed when converting date and/or time from character string. 242 16 0 The conversion of a %ls data type to a %ls data type resulted in an out-of-range value. 243 16 0 Type %.*ls is not a defined system type. 244 16 0 The conversion of the %ls value ‘%.*ls’ overflowed an %hs column. Use a larger integer column. 245 16 0 Conversion failed when converting the %ls value ‘%.*ls’ to data type %ls. 246 16 0 No anchor member was specified for recursive query «%.*ls». 247 16 0 An anchor member was found in the recursive part of recursive query «%.*ls». 248 16 0 The conversion of the %ls value ‘%.*ls’ overflowed an int column. 249 16 0 The type «%ls» is not comparable. It cannot be used in the %ls clause. 251 16 0 Could not allocate ancillary table for query optimization. Maximum number of tables in a query (%d) exceeded. 252 16 0 Recursive common table expression ‘%.*ls’ does not contain a top-level UNION ALL operator. 253 16 0 Recursive member of a common table expression ‘%.*ls’ has multiple recursive references. 254 16 0 Prefixed columns are not allowed in the column list of a PIVOT operator. 255 16 0 Pseudocolumns are not allowed in the column list of a PIVOT operator. 256 16 0 The data type %ls is invalid for the %ls function. Allowed types are: char/varchar, nchar/nvarchar, and binary/varbinary. 257 16 0 Implicit conversion from data type %ls to %ls is not allowed. Use the CONVERT function to run this query. 258 15 0 Cannot call methods on %ls. 259 16 0 Ad hoc updates to system catalogs are not allowed. 260 16 0 Disallowed implicit conversion from data type %ls to data type %ls, table ‘%.*ls’, column ‘%.*ls’. Use the CONVERT function to run this query. 261 16 0 ‘%.*ls’ is not a recognized function. 262 16 0 %ls permission denied in database ‘%.*ls’. 263 16 0 Must specify table to select from. 264 16 0 The column name ‘%.*ls’ is specified more than once in the SET clause or column list of an INSERT. A column cannot be assigned more than one value in the same clause. Modify the clause to make sure that a column is updated only once. If this statement updates or inserts columns into a view, column aliasing can conceal the duplication in your code. 265 16 0 The column name «%.*ls» specified in the %ls operator conflicts with the existing column name in the %ls argument. 266 16 0 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = %ld, current count = %ld. 267 16 0 Object ‘%.*ls’ cannot be found. 268 16 0 Cannot run SELECT INTO in this database. The database owner must run sp_dboption to enable this option. 270 16 0 Object ‘%.*ls’ cannot be modified. 271 16 0 The column «%.*ls» cannot be modified because it is either a computed column or is the result of a UNION operator. 272 16 0 Cannot update a timestamp column. 273 16 0 Cannot insert an explicit value into a timestamp column. Use INSERT with a column list to exclude the timestamp column, or insert a DEFAULT into the timestamp column. 275 16 0 Prefixes are not allowed in value or pivot columns of an UNPIVOT operator. 276 16 0 Pseudocolumns are not allowed as value or pivot columns of an UNPIVOT operator. 277 16 0 The column «%.*ls» is specified multiple times in the column list of the UNPIVOT operator. 278 16 0 The text, ntext, and image data types cannot be used in a GROUP BY clause. 279 16 0 The text, ntext, and image data types are invalid in this subquery or aggregate expression. 280 16 0 Only base table columns are allowed in the TEXTPTR function. 281 16 0 %d is not a valid style number when converting from %ls to a character string. 282 10 0 The ‘%.*ls’ procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be returned instead. 283 16 0 READTEXT cannot be used on inserted or deleted tables within an INSTEAD OF trigger. 284 16 0 Rules cannot be bound to text, ntext, or image data types. 285 16 0 The READTEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views or functions. 286 16 0 The logical tables INSERTED and DELETED cannot be updated. 287 16 0 The %ls statement is not allowed within a trigger. 288 16 0 The PATINDEX function operates on char, nchar, varchar, nvarchar, text, and ntext data types only. 289 16 0 Cannot construct data type %ls, some of the arguments have values which are not valid. 290 16 0 Invalid EXECUTE statement using object «%ls», method «%ls». 291 16 0 CAST or CONVERT: invalid attributes specified for type ‘%.*ls’ 292 16 0 There is insufficient result space to convert a smallmoney value to %ls. 293 16 0 Cannot convert char value to smallmoney. The char value has incorrect syntax. 294 16 0 The conversion from char data type to smallmoney data type resulted in a smallmoney overflow error. 295 16 0 Conversion failed when converting character string to smalldatetime data type. 297 16 0 The user does not have permission to perform this action. 300 14 0 %ls permission was denied on object ‘%.*ls’, database ‘%.*ls’. 301 16 0 Query contains an outer-join request that is not permitted. 302 16 0 The newsequentialid() built-in function can only be used in a DEFAULT expression for a column of type ‘uniqueidentifier’ in a CREATE TABLE or ALTER TABLE statement. It cannot be combined with other operators to form a complex scalar expression. 303 16 0 The table ‘%.*ls’ is an inner member of an outer-join clause. This is not allowed if the table also participates in a regular join clause. 304 16 0 ‘%I64d’ is out of range for index/statistics option ‘%.*ls’. See sp_configure option ‘%ls’ for valid values. 305 16 0 The XML data type cannot be compared or sorted, except when using the IS NULL operator. 306 16 0 The text, ntext, and image data types cannot be compared or sorted, except when using IS NULL or LIKE operator. 307 16 0 Index ID %d on table ‘%.*ls’ (specified in the FROM clause) does not exist. 308 16 0 Index ‘%.*ls’ on table ‘%.*ls’ (specified in the FROM clause) does not exist. 309 16 0 Cannot use index «%.*ls» on table «%.*ls» in a hint. XML indexes are not allowed in hints. 310 15 0 The value %d specified for the MAXRECURSION option exceeds the allowed maximum of %d. 311 16 0 Cannot use text, ntext, or image columns in the ‘inserted’ and ‘deleted’ tables. 312 16 0 Cannot reference text, ntext, or image columns in a filter stored procedure. 313 16 0 An insufficient number of arguments were supplied for the procedure or function %.*ls. 314 16 0 Cannot use GROUP BY ALL with the special tables INSERTED or DELETED. 315 16 0 Index «%.*ls» on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 316 16 0 The index ID %d on table «%.*ls» (specified in the FROM clause) is disabled or resides in a filegroup which is not online. 317 16 0 Table-valued function ‘%.*ls’ cannot have a column alias. 318 16 0 The table (and its columns) returned by a table-valued method need to be aliased. 319 16 0 Incorrect syntax near the keyword ‘with’. If this statement is a common table expression, an xmlnamespaces clause or a change tracking context clause, the previous statement must be terminated with a semicolon. 320 16 0 The compile-time variable value for ‘%.*ls’ in the OPTIMIZE FOR clause must be a literal. 321 15 0 «%.*ls» is not a recognized table hints option. If it is intended as a parameter to a table-valued function or to the CHANGETABLE function, ensure that your database compatibility mode is set to 90. 322 15 0 The variable «%.*ls» is specified in the OPTIMIZE FOR clause, but is not used in the query. 324 15 0 The ‘ALL’ version of the %.*ls operator is not supported. 325 15 0 Incorrect syntax near ‘%.*ls’. You may need to set the compatibility level of the current database to a higher value to enable this feature. See help for the SET COMPATIBILITY_LEVEL option of ALTER DATABASE. 326 16 0 Multi-part identifier ‘%.*ls’ is ambiguous. Both columns ‘%.*ls’ and ‘%.*ls’ exist. 327 16 0 Function call ‘%.*ls’ is ambiguous: both a user-defined function and a method call with this name exist. 328 16 0 A cursor plan could not be generated for the given statement because the textptr() function was used on a LOB column from one of the base tables. 329 16 0 Each GROUP BY expression must contain at least one column reference. 330 15 0 The target ‘%.*ls’ of the OUTPUT INTO clause cannot be a view or common table expression. 331 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled triggers. 332 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot be on either side of a (primary key, foreign key) relationship. Found reference constraint ‘%ls’. 333 15 0 The target table ‘%.*ls’ of the OUTPUT INTO clause cannot have any enabled check constraints or any enabled rules. Found check constraint or rule ‘%ls’. 334 15 0 The target table ‘%.*ls’ of the DML statement cannot have any enabled triggers if the statement contains an OUTPUT clause without INTO clause. 335 16 0 Function call cannot be used to match a target table in the FROM clause of a DELETE or UPDATE statement. Use function name ‘%.*ls’ without parameters instead. 336 15 0 Incorrect syntax near ‘%.*ls’. If this is intended to be a common table expression, you need to explicitly terminate the previous statement with a semi-colon. 337 10 0 Warning: the floating point value ‘%.*ls’ is too small. It will be interpreted as 0. 338 16 0 READEXT, WRITETEXT, and UPDATETEXT statements cannot be used with views, remote tables, and inserted or deleted tables inside triggers. 339 16 0 DEFAULT or NULL are not allowed as explicit identity values. 340 16 0 Cannot create the trigger «%.*ls» on view «%.*ls». AFTER triggers cannot be created on views. 341 16 0 Replication filter procedures may not contain columns of large object, large value, XML or CLR type. 342 16 0 Column «%.*ls» is not allowed in this context, and the user-defined function or aggregate «%.*ls» could not be found. 343 15 0 Unknown object type ‘%.*ls’ used in a CREATE, DROP, or ALTER statement. 344 16 0 Remote function reference ‘%.*ls’ is not allowed, and the column name ‘%.*ls’ could not be found or is ambiguous. 345 16 0 Function ‘%.*ls’ is not allowed in the OUTPUT clause, because it performs user or system data access, or is assumed to perform this access. A function is assumed by default to perform data access if it is not schemabound. 346 15 0 The parameter «%.*ls» can not be declared READONLY since it is not a table-valued parameter. 347 16 0 The table-valued parameter «%.*ls» cannot be declared as an OUTPUT parameter. 348 16 0 The table variable «%.*ls» can not be passed to a stored procedure with the OUTPUT option. 349 16 0 The procedure «%.*ls» has no parameter named «%.*ls». 350 16 0 The column «%.*ls» does not have a valid data type. A column cannot be of a user-defined table type. 351 16 0 Column, parameter, or variable %.*ls. : Cannot find data type %.*ls. 352 15 0 The table-valued parameter «%.*ls» must be declared with the READONLY option. 353 16 0 Function ‘%.*ls’ is not allowed in the %S_MSG clause when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. This is because the function performs user or system data access, or is assumed to perform this access. By default, a function is assumed to perform data access if it is not schema-bound. 354 16 0 The target ‘%.*ls’ of the INSERT statement cannot be a view or common table expression when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 355 16 0 The target table ‘%.*ls’ of the INSERT statement cannot have any enabled triggers when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. 356 16 0 The target table ‘%.*ls’ of the INSERT statement cannot be on either side of a (primary key, foreign key) relationship when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found reference constraint ‘%ls’. 357 16 0 The target table ‘%.*ls’ of the INSERT statement cannot have any enabled rules when the FROM clause contains a nested INSERT, UPDATE, DELETE, or MERGE statement. Found rule ‘%ls’. 358 16 0 The target table ‘%.*ls’ of the MERGE statement cannot have any enabled rules. Found rule ‘%ls’. 359 16 0 The target ‘%.*ls’ of an OUTPUT INTO clause has an index with the ignore_dup_key option and cannot be used when an OUTPUT clause is also used. 360 16 0 The target column list of an INSERT, UPDATE, or MERGE statement cannot contain both a sparse column and the column set that contains the sparse column. Rewrite the statement to include either the sparse column or the column set, but not both. 361 16 0 The number of target columns that are specified in an INSERT, UPDATE, or MERGE statement exceeds the maximum of %d. This total number includes identity, timestamp, and columns that have default values. To correct this error, change the query to target a sparse column set instead of single sparse columns. 362 16 0 The query processor could not produce a query plan because the name ‘%.*ls’ in the FORCESEEK hint on table or view ‘%.*ls’ did not match the key column names of the index ‘%.*ls’. 363 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the %S_MSG specified by index ‘%.*ls’. 364 16 0 The query processor could not produce a query plan because the FORCESEEK hint on view ‘%.*ls’ is used without a NOEXPAND hint. Resubmit the query with the NOEXPAND hint or remove the FORCESEEK hint on the view. 365 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ specified more seek columns than the number of key columns in index ‘%.*ls’. 366 16 0 The query processor could not produce a query plan because the FORCESEEK hint on table or view ‘%.*ls’ cannot be used with the column store index ‘%.*ls’. 367 16 0 The hint ‘%.*ls’ is valid only with memory optimized tables. 369 16 0 This operation is not supported on Windows Azure SQL Database with the TRCFLG_AUTO_PARTITION_REPLICATE traceflag turned on. 401 16 0 Unimplemented statement or expression %ls. 402 16 0 The data types %s and %s are incompatible in the %s operator. 403 16 0 Invalid operator for data type. Operator equals %ls, type equals %ls. 404 16 0 The column reference «%ls.%.*ls» is not allowed because it refers to a base table that is not being modified in this statement. 405 16 0 A remote table cannot be used as a DML target in a statement which includes an OUTPUT clause or a nested DML statement. 406 16 0 %ls cannot be used in the PIVOT operator because it is not invariant to NULLs. 407 16 0 Internal error. The string routine in file %hs, line %d failed with HRESULT 0x%x. 408 16 0 A constant expression was encountered in the ORDER BY list, position %i. 412 16 0 The column «%.*ls» is not updatable because it is derived or constant. 413 16 0 Correlated parameters or sub-queries are not supported by the inline function «%.*ls». 414 16 0 UPDATE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF UPDATE trigger. 415 16 0 DELETE is not allowed because the statement updates view «%.*ls» which participates in a join and has an INSTEAD OF DELETE trigger. 416 16 0 The service queue «%.*ls» cannot be directly updated. 417 16 0 TOP is not allowed in an UPDATE or DELETE statement against a partitioned view. 418 16 0 Objects exposing CLR type columns are not allowed in distributed queries. Use a pass-through query to access the remote object ‘%.*ls’. 421 16 0 The %ls data type cannot be selected as DISTINCT because it is not comparable. 422 16 0 Common table expression defined but not used. 423 16 0 Xml data type methods are not supported in check constraints. Create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». 424 16 0 Xml data type methods are not supported in computed column definitions of table variables and return tables of table-valued functions. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. 425 16 0 Data type %ls of receiving variable is not equal to the data type %ls of column ‘%.*ls’. 426 16 0 The length %d of the receiving variable is less than the length %d of the column ‘%.*ls’. 427 20 1 Could not load the definition for constraint ID %d in database ID %d. Run DBCC CHECKCATALOG to verify the integrity of the database. 428 16 0 Insert bulk cannot be used in a multi-statement batch. 432 16 0 Xml data type methods are not supported in check constraints anymore. Please drop the constraint or create a scalar user-defined function to wrap the method invocation. The error occurred at table «%.*ls». 434 16 0 Function ‘%ls’ is not allowed in the OUTPUT clause. 435 16 0 Xml data type methods are not supported in computed column definitions. Create a scalar user-defined function to wrap the method invocation. The error occurred at column «%.*ls», table «%.*ls», in the %ls statement. 438 16 0 Xml data type methods are not allowed in rules. The error occurred at table «%.*ls». 440 16 0 Internal query compilation error. The stack overflow could not be handled. 441 16 0 Cannot use the ‘%ls’ function on a remote data source. 442 16 0 The NEST argument must be a column reference. Expressions are not allowed. 443 16 0 Invalid use of a side-effecting operator ‘%s’ within a function. 444 16 0 Select statements included within a function cannot return data to a client. 446 16 0 Cannot resolve collation conflict between «%ls» and «%ls» in %ls operator for %ls operation. 447 16 0 Expression type %ls is invalid for COLLATE clause. 448 16 0 Invalid collation ‘%.*ls’. 449 16 0 Collation conflict caused by collate clauses with different collation ‘%.*ls’ and ‘%.*ls’. 450 16 0 Code page translations are not supported for the text data type. From: %d To: %d. 451 16 0 Cannot resolve collation conflict between «%ls» and «%ls» in %ls operator occurring in %ls statement column %d. 452 16 0 COLLATE clause cannot be used on user-defined data types. 453 16 0 Collation ‘%.*ls’ is supported on Unicode data types only and cannot be set at the database or server level. 454 16 0 The UNNEST argument must be a nested table column. 455 16 0 The last statement included within a function must be a return statement. 456 16 0 Implicit conversion of %ls value to %ls cannot be performed because the resulting collation is unresolved due to collation conflict between «%ls» and «%ls» in %ls operator. 457 16 0 Implicit conversion of %ls value to %ls cannot be performed because the collation of the value is unresolved due to a collation conflict between «%ls» and «%ls» in %ls operator. 458 16 0 Cannot create the SELECT INTO target table «%.*ls» because the xml column «%.*ls» is typed with a schema collection «%.*ls» from database «%.*ls». Xml columns cannot refer to schemata across databases. 459 16 0 Collation ‘%.*ls’ is supported on Unicode data types only and cannot be applied to char, varchar or text data types. 460 16 0 DISTINCT operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 461 16 0 The TOP or OFFSET operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 462 16 0 Outer join is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 463 16 0 Functions with parameters are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 464 16 0 Functions with side effects are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 465 16 0 Recursive references are not allowed in subqueries. 466 16 0 UNION operator is not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 467 16 0 GROUP BY, HAVING, or aggregate functions are not allowed in the recursive part of a recursive common table expression ‘%.*ls’. 468 16 0 Cannot resolve the collation conflict between «%.*ls» and «%.*ls» in the %ls operation. 469 16 0 An explicit column list must be specified for target table ‘%.*ls’ when table hint KEEPIDENTITY is used and the table contains an identity column. 470 16 0 The synonym «%.*ls» referenced synonym «%.*ls». Synonym chaining is not allowed. 471 16 0 Only one of the three options, SINGLE_BLOB, SINGLE_CLOB or SINGLE_NCLOB, can be specified. 472 16 0 Either a format file or one of the three options SINGLE_BLOB, SINGLE_CLOB, or SINGLE_NCLOB must be specified. 473 16 0 The incorrect value «%.*ls» is supplied in the PIVOT operator. 474 16 0 Unable to load the computed column definitions for table «%.*ls». 475 16 0 Invalid SAMPLE clause. Only table names in the FROM clause of SELECT, UPDATE, and DELETE queries may be sampled. 476 16 0 Invalid PERCENT tablesample size «%f» for table «%.*ls». The PERCENT tablesample size must be between 0 and 100. 477 16 0 Invalid ROWS value or REPEATABLE seed in the TABLESAMPLE clause for table «%.*ls». The value or seed must be an integer. 478 16 0 The TABLESAMPLE clause cannot be used in a view definition or inline table function definition. 479 16 0 Invalid ROWS value or REPEATABLE seed «%I64d» in the TABLESAMPLE clause for table «%.*ls». The value or seed must be greater than 0. 480 16 0 The TABLESAMPLE clause cannot be used with the table function «%.*ls». 481 16 0 The TABLESAMPLE clause cannot be used with the linked server table «%.*ls». 482 16 0 Non-constant or invalid expression is in the TABLESAMPLE or the REPEATABLE clause. 483 16 0 The OUTPUT clause cannot be used in an INSERT…EXEC statement. 484 16 0 Cannot declare more than %d local variables. 485 16 0 Views and inline functions cannot return xml columns that are typed with a schema collection registered in a database other than current. Column «%.*ls» is typed with the schema collection «%.*ls», which is registered in database «%.*ls». 486 16 0 «%.*ls» does not allow specifying a schema name as a prefix to the assembly name. 487 16 0 An invalid option was specified for the statement «%.*ls». 488 16 0 %s columns must be comparable. The type of column «%.*ls» is «%s», which is not comparable. 489 16 0 The OUTPUT clause cannot be specified because the target view «%.*ls» is a partitioned view. 490 16 0 The resync functionality is temporarily disabled. 491 16 0 A correlation name must be specified for the bulk rowset in the from clause. 492 16 0 Duplicate column names are not allowed in result sets obtained through OPENQUERY and OPENROWSET. The column name «%.*ls» is a duplicate. 493 16 0 The column ‘%.*ls’ that was returned from the nodes() method cannot be used directly. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 494 16 0 The TABLESAMPLE clause can only be used with local tables. 495 16 0 The return table column «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 496 16 0 The parameter «%.*ls» is not the same type as the type it was created with. Drop and recreate the module using a two-part name for the type, or use sp_refreshsqlmodule to refresh its parameters metadata. 497 16 0 Variables are not allowed in the TABLESAMPLE or REPEATABLE clauses. 498 16 0 Invalid value in the TABLESAMPLE or the REPEATABLE clause. 499 16 0 Invalid parameter for the getchecksum function. 500 16 0 Trying to pass a table-valued parameter with %d column(s) where the corresponding user-defined table type requires %d column(s). 505 16 0 The current user account was invoked with SETUSER or SP_SETAPPROLE. Changing databases is not allowed. 506 16 0 The invalid escape character «%.*ls» was specified in a %ls predicate. 507 16 0 Invalid argument for SET ROWCOUNT. Must be a non-null non-negative integer. 509 11 0 User name ‘%.*ls’ not found. 510 16 0 Cannot create a worktable row larger than allowable maximum. Resubmit your query with the ROBUST PLAN hint. 511 16 0 Cannot create a row of size %d which is greater than the allowable maximum row size of %d. 512 16 0 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression. 513 16 0 A column insert or update conflicts with a rule imposed by a previous CREATE RULE statement. The statement was terminated. The conflict occurred in database ‘%.*ls’, table ‘%.*ls’, column ‘%.*ls’. 515 16 0 Cannot insert the value NULL into column ‘%.*ls’, table ‘%.*ls’; column does not allow nulls. %ls fails. 517 16 0 Adding a value to a ‘%ls’ column caused an overflow. 518 16 0 Cannot convert data type %ls to %ls. 522 16 0 The WAITFOR thread was evicted. 523 16 0 A trigger returned a resultset and/or was running with SET NOCOUNT OFF while another outstanding result set was active. 524 16 0 A trigger returned a resultset and the server option ‘disallow results from triggers’ is true. 525 16 0 The column that was returned from the nodes() method cannot be converted to the data type %ls. It can only be used with one of the four XML data type methods, exist(), nodes(), query(), and value(), or in IS NULL and IS NOT NULL checks. 526 16 0 %ls of XML types constrained by different XML schema collections and/or DOCUMENT/CONTENT option is not allowed. Use the CONVERT function to run this query. 527 16 0 Implicit conversion between XML types constrained by different XML schema collections is not allowed. Use the CONVERT function to run this query. 529 16 0 Explicit conversion from data type %ls to %ls is not allowed. 530 16 0 The statement terminated. The maximum recursion %d has been exhausted before statement completion. 531 10 0 Cannot set NOCOUNT to OFF inside the trigger execution because the server option «disallow_results_from_triggers» is true or we are inside LOGON trigger execution. 532 16 0 The timestamp (changed to %S_TS) shows that the row has been updated by another user. 533 15 0 Cannot set XACT ABORT to OFF inside the trigger execution. 534 16 0 ‘%.*ls’ failed because it is not supported in the edition of this SQL Server instance ‘%.*ls’. See books online for more details on feature support in different SQL Server editions. 535 16 0 The %.*ls function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use %.*ls with a less precise datepart. 536 16 0 Invalid length parameter passed to the %ls function. 537 16 0 Invalid length parameter passed to the LEFT or SUBSTRING function. 539 16 0 Schema changed after the target table was created. Rerun the Select Into query. 540 16 1 There is insufficient system memory to run RAISERROR. 541 16 0 There is not enough stack to execute the statement 542 16 0 An invalid datetime value was encountered. Value exceeds the year 9999. 543 16 0 Creation of a return table failed for the table valued function ‘%.*ls’. 544 16 0 Cannot insert explicit value for identity column in table ‘%.*ls’ when IDENTITY_INSERT is set to OFF. 545 16 0 Explicit value must be specified for identity column in table ‘%.*ls’ either when IDENTITY_INSERT is set to ON or when a replication user is inserting into a NOT FOR REPLICATION identity column. 547 16 0 The %ls statement conflicted with the %ls constraint «%.*ls». The conflict occurred in database «%.*ls», table «%.*ls»%ls%.*ls%ls. 548 16 0 The insert failed. It conflicted with an identity range check constraint in database ‘%.*ls’, replicated table ‘%.*ls’%ls%.*ls%ls. If the identity column is automatically managed by replication, update the range as follows: for the Publisher, execute sp_adjustpublisheridentityrange; for the Subscriber, run the Distribution Agent or the Merge Agent. 549 16 0 The collation ‘%.*ls’ of receiving variable is not equal to the collation ‘%.*ls’ of column ‘%.*ls’. 550 16 0 The attempted insert or update failed because the target view either specifies WITH CHECK OPTION or spans a view that specifies WITH CHECK OPTION and one or more rows resulting from the operation did not qualify under the CHECK OPTION constraint. 552 16 0 CryptoAPI function ‘%ls’ failed. Error 0x%x: %ls 555 16 0 User-defined functions are not yet enabled. 556 16 0 INSERT EXEC failed because the stored procedure altered the schema of the target table. 557 16 0 Only functions and some extended stored procedures can be executed from within a function. 558 16 0 Remote function calls are not allowed within a function. 561 16 0 Failed to access file ‘%.*ls’ 562 16 0 Failed to access file ‘%.*ls’. Files can be accessed only through shares 563 14 0 The transaction for the INSERT EXEC statement has been rolled back. The INSERT EXEC operation will be terminated. 564 16 0 Attempted to create a record with a fixed length of ‘%d’. Maximum allowable fixed length is ‘%d’. 565 18 0 A stack overflow occurred in the server while compiling the query. Please simplify the query. 566 21 1 An error occurred while writing an audit trace. SQL Server is shutting down. Check and correct error conditions such as insufficient disk space, and then restart SQL Server. If the problem persists, disable auditing by starting the server at the command prompt with the «-f» switch, and using SP_CONFIGURE. 567 16 0 File ‘%.*ls’ is not a recognizable trace file. 568 16 0 Encountered an error or an unexpected end of trace file ‘%.*ls’. 569 16 0 The handle that was passed to %ls was invalid. 570 15 0 INSTEAD OF triggers do not support direct recursion. The trigger execution failed. 571 16 0 The specified attribute value for %ls is invalid. 572 16 0 Invalid regular expression «%.*ls» near the offset %d. 573 16 0 Evaluation of the regular expression is too complex: ‘%.*ls’. 574 16 0 %ls statement cannot be used inside a user transaction. 575 16 0 A LOGON trigger returned a resultset. Modify the LOGON trigger to not return resultsets. 576 16 0 Cannot create a row that has sparse data of size %d which is greater than the allowable maximum sparse data size of %d. 577 16 0 The value provided for the timeout is not valid. Timeout must be a valid integer between 0 and 2147483647. 578 16 0 Insert Exec not allowed in WAITFOR queries. 579 16 0 Can not execute WAITFOR query with snapshot isolation level. 582 16 0 Offset is greater than the length of the column to be updated in write. 583 16 0 Negative offset or length in write. 584 16 0 Select Into not allowed in WAITFOR queries. 585 16 0 Changing database context is not allowed when populating the resource database. 586 16 0 The prepared statement handle %d is not valid in this context. Please verify that current database, user default schema, and ANSI_NULLS and QUOTED_IDENTIFIER set options are not changed since the handle is prepared. 587 16 0 An invalid delayed CLR type fetch token is provided. 588 16 0 Multiple tasks within the session are using the same delayed CLR type fetch token at the same time. 589 16 0 This statement has attempted to access data whose access is restricted by the assembly. 590 16 0 RPC was aborted without execution. 591 16 0 %ls: The formal parameter «%ls» was defined as OUTPUT, but the actual parameter was not declared as OUTPUT. 592 16 0 Cannot find %S_MSG ID %d in database ID %d. 593 10 0 fn_trace_gettable: XML conversion of trace data for event 165 failed. 594 10 0 fn_trace_gettable: XML conversion of trace data is not supported in fiber mode. 595 16 0 Bulk Insert with another outstanding result set should be run with XACT_ABORT on. 596 16 0 Cannot continue the execution because the session is in the kill state. 597 16 0 The execution of in-proc data access is being terminated due to errors in the User Datagram Protocol (UDP). 598 16 0 An error occurred while executing CREATE/ALTER DB. Please look at the previous error for more information. 599 16 0 %.*ls: The length of the result exceeds the length limit (2GB) of the target large type. 601 12 0 Could not continue scan with NOLOCK due to data movement. 602 21 1 Could not find an entry for table or index with partition ID %I64d in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 603 21 1 Could not find an entry for table or index with object ID %d (partition ID %I64d) in database %d. This error can occur if a stored procedure references a dropped table, or metadata is corrupted. Drop and re-create the stored procedure, or execute DBCC CHECKDB. 605 21 1 Attempt to fetch logical page %S_PGID in database %d failed. It belongs to allocation unit %I64d not to %I64d. 606 21 1 Metadata inconsistency. Filegroup id %ld specified for table ‘%.*ls’ does not exist. Run DBCC CHECKDB or CHECKCATALOG. 608 16 1 No catalog entry found for partition ID %I64d in database %d. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption. 609 16 0 BTree is not empty when waking up on RowsetBulk. 610 16 1 Invalid header value from a page. Run DBCC CHECKDB to check for a data corruption. 611 16 0 Cannot insert or update a row because total variable column size, including overhead, is %d bytes more than the limit. 613 21 0 Could not find an entry for worktable rowset with partition ID %I64d in database %d. 614 16 0 Could not locate bookmark due to data movement. 615 21 1 Could not find database ID %d, name ‘%.*ls’. The database may be offline. Wait a few minutes and try again. 617 20 1 Descriptor for object ID %ld in database ID %d not found in the hash table during attempt to unhash it. A work table is missing an entry. Rerun the query. If a cursor is involved, close and reopen the cursor. 622 16 0 The filegroup «%.*ls» has no files assigned to it. Tables, indexes, text columns, ntext columns, and image columns cannot be populated on this filegroup until a file is added. 627 16 0 Cannot use SAVE TRANSACTION within a distributed transaction. 628 16 0 Cannot issue SAVE TRANSACTION when there is no active transaction. 650 16 0 You can only specify the READPAST lock in the READ COMMITTED or REPEATABLE READ isolation levels. 651 16 0 Cannot use the %ls granularity hint on the table «%.*ls» because locking at the specified granularity is inhibited. 652 16 0 The index «%.*ls» for table «%.*ls» (RowsetId %I64d) resides on a read-only filegroup («%.*ls»), which cannot be modified. 657 16 0 Could not disable support for %ls in database ‘%.*ls’ because %S_MSG. 658 16 0 Could not enable support for %ls in database ‘%.*ls’ because %S_MSG. 661 16 0 Cannot enable support for %ls in database ‘%.*ls’ because support for %ls is enabled and both are mutually exclusive. 666 16 0 The maximum system-generated unique value for a duplicate group was exceeded for index with partition ID %I64d. Dropping and re-creating the index may resolve this; otherwise, use another clustering key. 667 16 0 The index «%.*ls» for table «%.*ls» (RowsetId %I64d) resides on a filegroup («%.*ls») that cannot be accessed because it is offline, is being restored, or is defunct. 669 22 0 The row object is inconsistent. Please rerun the query. 670 16 0 Large object (LOB) data for table «%.*ls» resides on an offline filegroup («%.*ls») that cannot be accessed. 671 16 0 Large object (LOB) data for table «%.*ls» resides on a read-only filegroup («%.*ls»), which cannot be modified. 672 10 0 Failed to queue cleanup packets for orphaned rowsets in database «%.*ls». Some disk space may be wasted. Cleanup will be attempted again on database restart. 674 10 1 Exception occurred in destructor of RowsetNewSS 0x%p. This error may indicate a problem related to releasing pre-allocated disk blocks used during bulk-insert operations. Restart the server to resolve this problem. 675 10 1 Worktable with partition ID %I64d was dropped successfully after %d repeated attempts. 676 10 1 Error occurred while attempting to drop worktable with partition ID %I64d. 677 10 1 Unable to drop worktable with partition ID %I64d after repeated attempts. Worktable is marked for deferred drop. This is an informational message only. No user action is required. 678 10 1 Active rowset for partition ID %I64d found at the end of the batch. This error may indicate incorrect exception handling. Use the current activity window in SQL Server Management Studio or the Transact-SQL KILL statement to terminate the server process identifier (SPID) responsible for generating the error. 679 16 0 One of the partitions of index ‘%.*ls’ for table ‘%.*ls'(partition ID %I64d) resides on a filegroup («%.*ls») that cannot be accessed because it is offline, restoring, or defunct. This may limit the query result. 680 10 1 Error [%d, %d, %d] occurred while attempting to drop allocation unit ID %I64d belonging to worktable with partition ID %I64d. 681 16 0 Attempting to set a non-NULL-able column’s value to NULL. 682 16 0 Internal error. Buffer provided to read column value is too small. Run DBCC CHECKDB to check for any corruption. 683 22 0 An internal error occurred while trying to convert between variable-length and fixed-length decimal formats. Run DBCC CHECKDB to check for any database corruption. 684 22 0 An internal error occurred while attempting to convert between compressed and uncompressed storage formats. Run DBCC CHECKDB to check for any corruption. 685 22 0 An internal error occurred while attempting to retrieve a backpointer for a heap forwarded record. 686 22 0 The maximum level of the B-Tree for rowset %I64d has been reached. SQL Server only supports upto 255 levels. 687 16 0 Cannot compress a nchar or nvarchar column that has an odd number of bytes. 688 16 0 Operation not allowed due to an active online index build. 689 16 0 Operation not allowed because of pending cleanup of online index build. Wait for cleanup to complete and re-run the operation. 691 16 1 An internal error occurred. Error code %X. 692 16 0 Internal error. Buffer provided to write a fixed column value is too large. Run DBCC CHECKDB to check for any corruption. 694 16 0 Internal error. Unable to create a block blob in Azure storage. 695 16 0 Internal error. Unable to delete a block blob in Azure storage. 696 16 0 Internal error. Unable to gain access to the tombstone table. 697 16 0 Internal error. Unable to get a blob storage container. 701 19 1 There is insufficient system memory in resource pool ‘%ls’ to run this query. 708 10 1 Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used %d times since startup. Cancel query and re-run, decrease server load, or cancel other applications. 801 20 1 A buffer was encountered with an unexpected status of 0x%x. 802 17 0 There is insufficient memory available in the buffer pool. 803 10 1 simulated failure (DEBUG only) 805 10 1 restore pending 806 10 1 audit failure (a page read from disk failed to pass basic integrity checks) 807 10 1 (no disk or the wrong disk is in the drive) 808 10 1 Insufficient bytes transferred. Common causes are backup configuration, insufficient disk space, or other problems with the storage subsystem such as corruption or hardware failure. Check errorlogs/application-logs for detailed messages and correct error conditions. 821 20 1 Could not unhash buffer at 0x%p with a buffer page number of %S_PGID and database ID %d with HASHED status set. The buffer was not found. %S_PAGE. Contact Technical Support. 822 21 1 Could not start I/O operation for request %S_BLKIOPTR. Contact Technical Support. 823 24 1 The operating system returned error %ls to SQL Server during a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 824 24 1 SQL Server detected a logical consistency-based I/O error: %ls. It occurred during a %S_MSG of page %S_PGID in database ID %d at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log or operating system error log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 825 10 1 A read of the file ‘%ls’ at offset %#016I64x succeeded after failing %d time(s) with error: %ls. Additional messages in the SQL Server error log and operating system error log may provide more detail. This error condition threatens database integrity and must be corrected. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 826 10 1 incorrect pageid (expected %d:%d; actual %d:%d) 829 21 1 Database ID %d, Page %S_PGID is marked RestorePending, which may indicate disk corruption. To recover from this state, perform a restore. 830 10 0 stale page (a page read returned a log sequence number (LSN) (%u:%u:%u) that is older than the last one that was written (%u:%u:%u)) 831 20 0 Unable to deallocate a kept page. 832 24 1 A page that should have been constant has changed (expected checksum: %08x, actual checksum: %08x, database %d, file ‘%ls’, page %S_PGID). This usually indicates a memory failure or other hardware or OS corruption. 833 10 0 SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database id %d. The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x 835 16 0 The operating system returned error %ls to SQL Server. It failed creating event for a %S_MSG at offset %#016I64x in file ‘%ls’. Additional messages in the SQL Server error log and operating system error log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. 844 10 0 Time out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait. 845 17 0 Time-out occurred while waiting for buffer latch type %d for page %S_PGID, database ID %d. 846 10 0 A time-out occurred while waiting for buffer latch — type %d, bp %p, page %d:%d, stat %#x, database id: %d, allocation unit Id: %I64d%ls, task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Not continuing to wait. 847 10 1 Timeout occurred while waiting for latch: class ‘%ls’, id %p, type %d, Task 0x%p : %d, waittime %d seconds, flags 0x%I64x, owning task 0x%p. Continuing to wait. 848 10 1 Using large pages in the memory manager. 849 10 1 Using locked pages in the memory manager. 850 10 1 %I64u MB of large page memory allocated. 851 10 0 the page is in an OFFLINE file which cannot be read 852 10 1 Using conventional memory in the memory manager. 853 10 0 Latch acquire failed due to too many concurrent latches. type %d, Task 0x%p : %d 854 10 1 Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption. 855 10 1 Uncorrectable hardware memory corruption detected. Your system may become unstable. Please check the operating system error log for more details. 856 10 1 SQL Server has detected hardware memory corruption in database ‘%ls’, file ID: %u, page ID; %u, memory address: 0x%I64x and has successfully recovered the page. 857 10 0 Buffer pool extension «%.*ls» has been initialized successfully with size is %I64d MB. 858 10 0 Failed to create buffer pool extension of size %I64d MB on path «%.*ls». 859 10 1 Buffer pool extension configuration «%.*ls» is in wrong format. The format should be «<extension directory>,<size in GB>». 860 10 1 %ls. BUF address 0x%x. Bufno %u. Extension offset %1I64d. Error code %d. Database file id %u. Database file offset %2I64d. 861 10 1 Buffer pool extension size must be larger than the physical memory size %I64d MB. Buffer pool extension is not enabled. 862 10 1 Attempt to disable buffer pool extension when in state %ls is not allowed. 863 10 1 Attempt to enable buffer pool extension when in state %ls is not allowed. 864 10 1 Attempted to initialize buffer pool extension of size %1ld KB, but maximum allowed size is %2ld KB. 865 10 1 Buffer pool extension is only supported on Standard and Enterprise Editions of SQL Server. 866 10 1 Buffer pool extension is not supported on the %ls architecture. 867 10 0 Buffer pool extension has been disabled successfully. Deleting buffer pool extension «%.*ls». 868 10 1 Buffer pool extension size must be larger than the current memory allocation threshold %I64d MB. Buffer pool extension is not enabled. 869 10 1 Buffer pool extension «%.*ls» cannot be closed because %ld asynchronous I/Os are outstanding. 870 10 1 BPE feature switch is on! 871 10 1 Buffer pool extension size from RG Setting is %d GB (%I64d bytes). 872 10 1 Buffer pool extension is already enabled. No action is necessary. 873 10 1 Buffer pool extension is already disabled. No action is necessary. 874 10 0 Failed to initialize resilient buffer pool extension of size %I64d MB on path «%.*ls». 875 10 0 Resilient buffer pool extension «%.*ls» has been started successfully with size is %I64d MB. 876 10 0 Failed to startup resilient buffer pool extension of size %I64d MB on path «%.*ls». 877 10 0 Resilient buffer pool extension «%.*ls» has been enabled successfully with size %I64d MB. 878 10 0 Failed to create resilient buffer pool extension of size %I64d MB on path «%.*ls». 879 10 0 Failed to start resilient buffer pool extension because database %d is not memory optimized. 880 10 0 Failed to find the metadata of resilient buffer pool extension in database %d. 881 10 1 Resilient buffer pool extension is already disabled. No action is necessary. 882 22 0 The schema of a table created by InternalBaseTable is corrupt. 883 16 0 Could not create the Write Page Recorder table: wpr_bucket_table for database %ls. 884 16 0 Could not persist a bucket to the Write Page Recorder table: wpr_bucket_table for database %ls. 885 16 1 An internal error occurred. Error code %X. Context: «%ls::%d». 886 10 1 Resilient buffer pool extension is already enabled. No action is necessary. 891 10 1 Buffer pool extension is not supported on %ls platform. 902 16 0 To change the %ls, the database must be in state in which a checkpoint can be executed. 904 16 0 Database %ld cannot be autostarted during server shutdown or startup. 905 21 1 Database ‘%.*ls’ cannot be started in this edition of SQL Server because it contains a partition function ‘%.*ls’. Only Enterprise edition of SQL Server supports partitioning. 907 16 0 The database «%ls» has inconsistent database or file metadata. 908 10 1 Filegroup %ls in database %ls is unavailable because it is %ls. Restore or alter the filegroup to be available. 909 21 1 Database ‘%.*ls’ cannot be started in this edition of SQL Server because part or all of object ‘%.*ls’ is enabled with data compression or vardecimal storage format. Data compression and vardecimal storage format are only supported on SQL Server Enterprise Edition. 910 10 0 Database ‘%.*ls’ is upgrading script ‘%.*ls’ from level %d to level %d. 911 16 0 Database ‘%.*ls’ does not exist. Make sure that the name is entered correctly. 912 21 0 Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ encountered error %d, state %d, severity %d. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 913 22 1 Could not find database ID %d. Database may not be activated yet or may be in transition. Reissue the query once the database is available. If you do not think this error is due to a database that is transitioning its state and this error continues to occur, contact your primary support provider. Please have available for review the Microsoft SQL Server error log and any additional information relevant to the circumstances when the error occurred. 914 21 0 Script level upgrade for database ‘%.*ls’ failed because upgrade step ‘%.*ls’ was aborted before completion. If the abort happened during upgrade of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion. 915 21 0 Unable to obtain the current script level for database ‘%.*ls’. If the error happened during startup of the ‘master’ database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that script upgrade may run to completion. 916 14 0 The server principal «%.*ls» is not able to access the database «%.*ls» under the current security context. 917 21 0 An upgrade script batch failed to execute for database ‘%.*ls’ due to compilation error. Check the previous error message for the line which caused compilation to fail. 918 21 0 Failed to load the engine script metadata from script DLL ‘%.*ls’. The error code reported by the operating system was %d. This is a serious error condition, which usually indicates a corrupt or incomplete installation. Repairing the SQL Server instance may help resolve this error. 919 10 0 User ‘%.*ls’ is changing database script level entry %d to a value of %d. 920 20 0 Only members of the sysadmin role can modify the database script level. 921 14 0 Database ‘%.*ls’ has not been recovered yet. Wait and try again. 922 14 0 Database ‘%.*ls’ is being recovered. Waiting until recovery is finished. 923 14 0 Database ‘%.*ls’ is in restricted mode. Only the database owner and members of the dbcreator and sysadmin roles can access it. 924 14 0 Database ‘%.*ls’ is already open and can only have one user at a time. 925 19 1 Maximum number of databases used for each query has been exceeded. The maximum allowed is %d. 926 14 0 Database ‘%.*ls’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. 927 14 0 Database ‘%.*ls’ cannot be opened. It is in the middle of a restore. 928 20 1 During upgrade, database raised exception %d, severity %d, state %d, address %p. Use the exception number to determine the cause. 929 20 1 Unable to close a database that is not currently open. The application should reconnect and try again. If this action does not correct the problem, contact your primary support provider. 930 21 1 Attempting to reference recovery unit %d in database ‘%ls’ which does not exist. Contact Technical Support. 931 21 1 Attempting to reference database fragment %d in database ‘%ls’ which does not exist. Contact Technical Support. 932 21 1 SQL Server cannot load database ‘%.*ls’ because change tracking is enabled. The currently installed edition of SQL Server does not support change tracking. Either disable change tracking in the database by using a supported edition of SQL Server, or upgrade the instance to one that supports change tracking. 933 21 1 Database ‘%.*ls’ cannot be started because some of the database functionality is not available in the current edition of SQL Server. 934 21 1 SQL Server cannot load database ‘%.*ls’ because Change Data Capture is enabled. The currently installed edition of SQL Server does not support Change Data Capture. Either restore database without KEEP_CDC option, or upgrade the instance to one that supports Change Data Capture. 935 21 1 The script level for ‘%.*ls’ in database ‘%.*ls’ cannot be downgraded from %d to %d, which is supported by this server. This usually implies that a future database was attached and the downgrade path is not supported by the current installation. Install a newer version of SQL Server and re-try opening the database. 936 16 0 Database ‘%.*ls’ can not be used in this edition of SQL Server. 937 21 1 Database ‘%.*ls’ cannot be upgraded because ‘%.*ls’ functionality is not available in the current edition of SQL Server. 938 21 1 The target database version %d is not supported by the current code version %d. Change target version to a supported level and restart the server. 941 16 0 Database ‘%.*ls’ cannot be opened because it is not started. Retry when the database is started. 942 14 0 Database ‘%.*ls’ cannot be opened because it is offline. 943 14 0 Database ‘%.*ls’ cannot be opened because its version (%d) is later than the current server version (%d). 944 10 0 Converting database ‘%.*ls’ from version %d to the current version %d. 945 16 0 Database ‘%.*ls’ cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 946 14 1 Cannot open database ‘%.*ls’ version %d. Upgrade the database to the latest version. 947 16 1 Error while closing database ‘%.*ls’. Check for previous additional errors and retry the operation. 948 20 1 The database ‘%.*ls’ cannot be opened because it is version %d. This server supports version %d and earlier. A downgrade path is not supported. 949 16 0 tempdb is skipped. You cannot run a query that requires tempdb 950 20 1 Database ‘%.*ls’ cannot be upgraded because its non-release version (%d) is not supported by this version of SQL Server. You cannot open a database that is incompatible with this version of sqlservr.exe. You must re-create the database. 951 10 0 Database ‘%.*ls’ running the upgrade step from version %d to version %d. 952 16 0 Database ‘%.*ls’ is in transition. Try the statement later. 954 14 0 The database «%.*ls» cannot be opened. It is acting as a mirror database. 955 14 0 Database %.*ls is enabled for Database Mirroring, but the database lacks quorum: the database cannot be opened. Check the partner and witness connections if configured. 956 14 0 Database %.*ls is enabled for Database Mirroring, but has not yet synchronized with its partner. Try the operation again later. 957 17 0 Database ‘%.*ls’ is enabled for database mirroring or has joined an availability group. The name of the database cannot be changed. 958 10 1 The resource database build version is %.*ls. This is an informational message only. No user action is required. 959 20 1 The resource database version is %d and this server supports version %d. Restore the correct version or reinstall SQL Server. 960 10 0 Warning: User «sys» (principal_id = %d) in database «%.*ls» has been renamed to «%.*ls». «sys» is a reserved user or schema name in this version of SQL Server. 961 10 0 Warning: Index «%.*ls» (index_id = %d) on object ID %d in database «%.*ls» was renamed to «%.*ls» because its name is a duplicate of another index on the same object. 962 10 0 Warning: Primary key or Unique constraint «%.*ls» (object_id = %d) in database «%.*ls» was renamed to «%.*ls» because its index was renamed. 963 10 0 Warning: Database «%.*ls» was marked suspect because of actions taken during upgrade. See errorlog or eventlog for more information. Use ALTER DATABASE to bring the database online. The database will come online in restricted_user state. 964 10 0 Warning: System user ‘%.*ls’ was found missing from database ‘%.*ls’ and has been restored. This user is required for SQL Server operation. 965 10 0 Warning: A column nullability inconsistency was detected in the metadata of index «%.*ls» (index_id = %d) on object ID %d in database «%.*ls». The index may be corrupt. Run DBCC CHECKTABLE to verify consistency. 966 10 0 Warning: Assembly «%.*ls» in database «%.*ls» has been renamed to «%.*ls» because the name of the assembly conflicts with a system assembly in this version of SQL Server. 967 10 0 Warning: The index «%.*ls» on «%.*ls».»%.*ls» is disabled because the XML data bound to it may contain negative values for xs:date and xs:dateTime which are not longer supported. 968 10 0 Warning: The XML facet on type «%.*ls» in schema collection «%.*ls» is updated from «%.*ls» to «%.*ls» because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 969 10 0 Warning: The default or fixed value on XML element or attribute «%.*ls» in schema collection «%.*ls» is updated from «%.*ls» to «%.*ls» because Sql Server does not support negative years inside values of type xs:date or xs:dateTime. 970 10 0 Warning: The XML instances in the XML column «%.*ls.%.*ls.%.*ls» may contain negative simple type values of type xs:date or xs:dateTime. It will be impossible to run XQuery or build a primary or selective XML index on these XML instances. 971 10 0 The resource database has been detected in two different locations. Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ instead of the currently attached resource database at ‘%.*ls’. 972 17 0 Could not use database ‘%d’ during procedure execution. 974 10 0 Attaching the resource database in the same directory as sqlservr.exe at ‘%.*ls’ failed as the database files do not exist. 975 10 1 System objects could not be updated in database ‘%.*ls’ because it is read-only. 976 14 0 The target database, ‘%.*ls’, is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online. 977 10 0 Warning: Could not find associated index for the constraint ‘%.*ls’ on object_id ‘%d’ in database ‘%.*ls’. 978 14 0 The target database (‘%.*ls’) is in an availability group and is currently accessible for connections when the application intent is set to read only. For more information about application intent, see SQL Server Books Online. 979 14 0 The target database (‘%.*ls’) is in an availability group and currently does not allow read only connections. For more information about application intent, see SQL Server Books Online. 980 21 1 SQL Server cannot load database ‘%.*ls’ because it contains a columnstore index. The currently installed edition of SQL Server does not support columnstore indexes. Either disable the columnstore index in the database by using a supported edition of SQL Server, or upgrade the instance of SQL Server to a version that supports columnstore index. 981 10 0 Database manager will be using %d target database version. 982 14 0 Unable to access the ‘%.*ls’ database because no online secondary replicas are enabled for read-only access. Check the availability group configuration to verify that at least one secondary replica is configured for read-only access. Wait for an enabled replica to come online, and retry your read-only operation. 983 14 0 Unable to access availability database ‘%.*ls’ because the database replica is not in the PRIMARY or SECONDARY role. Connections to an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later. 984 21 1 Failed to perform a versioned copy of sqlscriptdowngrade.dll from Binn to BinnCache folder. VerInstallFile API failed with error code %d. 985 10 1 Successfully installed the file ‘%ls’ into folder ‘%ls’. 986 10 0 Couldn’t get a clean bootpage for database ‘%.*ls’ after %d tries. This is an informational message only. No user action is required. 987 23 1 A duplicate key insert was hit when updating system objects in database ‘%.*ls’. 988 14 0 Unable to access database ‘%.*ls’ because it lacks a quorum of nodes for high availability. Try the operation again later. 989 16 0 Failed to take the host database with ID %d offline when one or more of its partition databases is marked as suspect. 990 16 0 Taking the host database with ID %d offline because one or more of its partition databases is marked as suspect. 991 16 0 Failed to take the host database ‘%.*ls’ offline when one or more of its partition databases is marked as suspect. 992 16 0 Failed to get the shared lock on database ‘%.*ls’. 993 10 0 Redo for database ‘%.*ls’ applied version upgrade step from %d to %d. 994 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled because it contains a computed column. 995 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled. It cannot be upgraded as it resides on a read-only filegroup. 996 10 0 Warning: Index «%.*ls» on «%.*ls».»%.*ls» is disabled. This columnstore index cannot be upgraded, likely because it exceeds the row size limit of ‘%d’ bytes.