sqlserver2000错误信息解释(SQLServer2000错误信息解释)

sql server 2000 错误信息解释（SQL Server 2000错误信息解释）

Description of error severity (message text)

110 last upgrade version date: 10/11/90.

2110 warning: serious error%1! Occurred in%2!. Please note the

error and time, and then contact the system administrator.

10215 syntax errors near''%1!!'.

10315%1 with''%2 Too long. The maximum length is%4!.

10415 if the statement contains the UNION operator, then the

items in the ORDER BY clause must appear in the selection list.

10515 string''%1!! 'before there is an unclosed quotation mark.

10616 there are too many table names in the query. The maximum

allowable number is%1!.

The 10715 column prefix''%1 '' does not match the table name

or alias used in the query.

The position of%1 10815 ORDER in the BY clause exceeds the

number of items in the select list.

The number of columns in the 10915 INSERT statement is greater

than the number specified in the VALUES clause. The number of

VALUES clauses must be matched to the number of columns

specified in the INSERT statement.

The number of columns in the 11015 INSERT statement is less than

the number specified in the VALUES clause. The number of VALUES

clauses must be matched to the number of columns specified in

the INSERT statement.

11115''%1! 'must be the first statement in the batch query.

11215%1! No variables are allowed in the statement.

11315 short notes at the end of'*/'mark.

11415 invalid access mode for statements that assign values to

variables.

11615 when you do not introduce a subquery with EXISTS, you can

only specify an expression in the selection list.

11715%1! Name''%2! 'contains the number of prefixes greater

than the maximum value. The maximum value is%4!.

11815 only the members of the sysadmin role can specify the%1!%2

option of the statement.

11915, you must pass the number of parameters%1, and pass the

following parameters in the form of'@name = value'. Once

the'@name = value'form is used, all subsequent parameters must

be passed in the form of'@name = value'.

The selection list of the 12015 INSERT statement contains less

entries than that in the insert list. The number of SELECT

statements must match the number of columns in the INSERT

statement.

The selection list of the 12115 INSERT statement contains more

entries than that in the insert list. The number of SELECT

statements must match the number of columns in the INSERT

statement.

12215%1! Options are allowed only for%2! Syntax.

The 12315 batch / process exceeds the maximum length of%1

characters.

12415 CREATE PROCEDURE does not contain any statements.

The 12515 Case expression can only be nested into the%1! Layer.

12815 the name''%1! 'is not allowed in this context. Only

constants, expressions, or variables are allowed here. Column

names are not allowed.

12915 fill factor%1! Is an invalid percentage; fill factor must

be between 1 and 100.

13016 cannot aggregate functions with expressions that contain

aggregations or sub queries.

13115 gives the size of "%2!''%3!!". (%1!) exceeds the maximum

allowed value of any data type (%5!).

13215 tag''%1!! 'has been declared. Tag names must be unique

within batch queries or stored procedures.

The 13315 GOTO statement points to the label''%1 '', but the

tag has not yet been declared.

The 13415 variable name''%1!! 'has been declared. Variable

names must be unique within a batch query or stored procedure.

13515 cannot use the BREAK statement outside the scope of the

WHILE statement.

13615 cannot use the CONTINUE statement outside the scope of

the WHILE statement.

13715 must declare variable''%1! ''.

13815 do not allow relative clauses to be used in subquery.

13915 cannot assign default values to local variables.

140 15 只能在 create trigger 语句内部使用 if update.

141 15 向变量赋值的 select 语句不能与数据检索操作结合使用.

142 15 约束 ''% 1! " 的定义中有错误语法.

143 15 在排序依据列表中没有找到 compute by 子句中的某一项.计算依据列表中的所有表达式也必须同时出现在排序依据列表中.

144 15 在用于 group by 子句分组依据列表的表达式中, 不能使用聚合或子查询.

145 15 如果指定了 select distinct, 那么 by order of 子句中的项就必须出现在选择列表中.

146 15 未能为子查询分配辅助表.超出了查询中表数目的最大值 (%

1! ).

147 15 聚合不应出现在 where 子句中, 除非该聚合位于 having

子句或选择列表所包含的子查询中, 并且要对其进行聚合的列是外部引用.

148 15 waitfor 所用的时间字符串 ''% 1! " 中时间语法有误.

149 15 waitfor 所用的时间值 ''% 1! " 是无效值.请检查日期 / 时间语法.

150 15 外联接的两项都必须包含列.

151 to 15 ''% 1! " 是无效 money 值.

153 15 在% 3! 语句中有% 1! 选项的无效使用.

154 of 15 在% 2! 中不允许使用% 1! .

155 15 ''% 1! " 不是可以识别的% 3! 选项.

156 15 在关键字 ''% 1! " 附近有语法错误.

157 15 聚合不应出现在 update 语句的集合列表中.

159 15 对于 drop index, 必须以 ame 的形式同时给出表名和索引名.

160 15 规则不包含变量.

161 15 规则包含多个变量.

163 15 计算依据列表与排序依据列表不匹配.

164 15 group by 表达式必须引用出现在选择列表中的列名.

165 16 不能授予或废除特权% 1! .

166 15 ''% 1! " 不允许将数据库名称指定为对象名前缀.

167 16 不能在临时对象上创建触发器.

168 of 15% 1! " % 2! " 超出了计算机表示范围 (% 4! 字节).

169 15 在排序依据列表中多次指定了某一列.排序依据列表中的列必须是唯一的.

170 15 第% 1! 行: 在 ''% 1! " 附近有语法错误.

171 15 不能在浏览模式中使用 select into.

172 15 不能在浏览模式中使用 holdlock.

173 15 列 ''% 1! " 的定义中必须包括数据类型.

174 15% 1! 函数要求有% 2! 个参数.

177 15 仅当 select 语句中有 into 子句时, 才能使用 identity

函数.

178 15 在此上下文中不能使用带有返回值的 return 语句.

179 15 向存储过程传递常量时不能使用 output 选项.

180 15 此% 1! 语句中参数太多.参数最大数目为% 2! .

181 15 不能在 declare 语句中使用 output 选项.

182 15 必须为 readtext 或 writetext 实用工具提供表名和列名.

183 15 列 ''% 2! " 的小数位数 (% 1! ) 必须介于% 4! 到% 5. 之间.

185, 15 数据流在大容量形式下的 writetext 语句中无效.

186 15 writetext 语句中缺少数据流.

188 15 在 create database 语句中, 如果不同时指定至少一个非日志设备, 就不能指定日志设备.

189 15% 1! 函数要求有% 2! 到% 3! 个参数.

191 15 sql 语句的某些部分嵌套过深.

Please rewrite the query or decompose it into several smaller

queries.

19216 decimal digits must be less than or equal to accuracy.

19315 the object name or column name at the beginning of''%1!

'is too long. The maximum length is%3! A character.

The 19415 SELECT INTO statement cannot contain the SELECT

statement assigned to the variable.

19515''%1!! 'is not an%3 that can be identified!.

The 19615 SELECT INTO must be the first query in the SQL

statement containing the UNION operator.

19715 cannot use EXECUTE as a source when inserting variables

into a table.

The 19815 browse mode is invalid for statements containing the

UNION operator.

The 19915 INSERT statement cannot contain the SELECT statement

assigned to the variable.

The 20116 procedure''%1! 'requires parameter''%3'! ', but this

parameter is not provided.

20216 WAITFOR type''%1! 'invalid. The supported data types are

CHAR/VARCHAR, NCHAR/NVARCHAR and DATETIME. WAITFOR DELAY also

supports INT and SMALLINT data types.

The 20316 name''%1!! 'is not a valid identifier.

20420 a normalization error occurred in node%1.

20516 all queries in the SQL statement containing the UNION

operator must have the same number of expressions in the target

list.

20616 operand type conflict:%1! Incompatible with%2!

20716 column''%1!! invalid.

20816 object name''%1 '' invalid.

20916 column names''%1! 'unclear.

21016 syntax error when converting from binary/varbinary

string to datetime.

21216 the length of the expression result exceeds the maximum

limit. The maximum value is%1, but the current length is%2!.

21316 insert error: the column name or the number of supplied

values does not match the table definition.

The 21416 procedure requires the parameter''%1! ''''%2 '' type.

21716 exceeds the maximum number of layers of stored procedures,

functions, triggers, or views (maximum number of layers is%1!).

22016 arithmetic overflow error occurred in data type%1 = value

=%2!.

22110 FIPS warning: implicit transformation from%1 to%2.

The 22311 object ID%1! Is specified as the default value of

column ID%3 in table ID%2!, but the object is missing or not

the default value type.

The 22411 object ID%1! Is specified as the rule of column ID%3

in table ID%2!, but the object is missing or not the default

value type.

22616%1 statement is not allowed in multi statement

transactions.

22914 rejected the%1 permissions for object''%2!

"(database''%4! ', owner''%6!' ').

23014 rejected the%1! Permissions of column''%2!

"(database''%6! ', owner''%8!') for object''%4!!'.

23111 there is no such default value. ID =%1! Database ID =%2!.

23216 arithmetic overflow error of type%1! = value =%2!.

The column''%1!! 'in table 23316'!''%3!! 'cannot be empty.

23416, the result space is insufficient, can not convert money

value to%1!.

23516 cannot convert char value to money. The syntax of the char

value is incorrect.

23616 money overflow error caused by the conversion from char

data type to money data type.

23716, the result space is insufficient, can not convert money

value to%1!.

23816 the result space is insufficient, can't convert the%1

value (=%2!) to the money data type.

24116 syntax errors from string to datetime.

24216 conversion from char data type to datetime data type leads

to datetime value cross boundary.

24316 type%1! Is not a defined system type.

"24416%1! Value''%2!!" conversion overflowed the%4! Column.

Please use a larger integer column.

24516 syntax error when converting%1! Value''%2!! 'to a column

with data type%4!.

"24816%1! Value''%2!!" conversion overflowed the int column.

Exceeded the maximum integer value.

25116 failed to allocate auxiliary tables for query

optimization. Exceeded the maximum number of tables in the

query (%1!).

25616 data type%1! Invalid for function%2. The allowed types

are: char/varchar, nchar/nvarchar, and binary/varbinary.

25716 implicit conversion from data type%1 to%2 is not allowed.

Use the CONVERT function to run this query.

25916 a special update to the system directory is not enabled.

The system administrator must reconfigure the SQL Server to

allow this operation.

26016 the implicit conversion from data type%1 to data type%2

is not allowed (table''%3 ', column''%5' '). Use the CONVERT

function to run this query.

26116''%1!! 'is not a recognized function.

26216 deny%1! Permissions in database''%2!'.

26316 must specify the table to choose from.

26416 column name''%1 "" appears many times in the list of

result columns.

The transaction count after 26616 EXECUTE indicates that the

COMMIT or ROLLBACK TRANSACTION statement is missing. Original

count =%1! Current count =%2!.

26716 cannot find object''%1! ''.

26816 cannot run SELECT INTO in this database. The database

owner must run sp_dboption to enable this option.

27016 cannot modify object''%1 ''.

27116 cannot modify column''%1 '' because the column is a

computed column.

27216 cannot update the timestamp column.

27316 cannot insert non null values in the timestamp column.

Use INSERT statements with columns or timestamp columns with

default values of NULL.

27816 the text, ntext, and image data types cannot be used in

the GROUP BY clause.

27916 in this subquery or aggregation expression, text, ntext,

and image data types are invalid.

28016 for TEXTPTR functions, only text, ntext, and image

columns are valid.

28116 when%2 is converted to a string,%1 is an invalid style

number.

The 28210 process''%1 '' tries to return to the state value NULL,

but this is not allowed. Will be returned to the state value

0.

28316 within INSTEAD OF triggers, READTEXT cannot be used for

inserted or deleted tables.

28416 cannot bind rules to text, ntext, or image data types.

28516 READTEXT, WRITETEXT, and UPDATETEXT statements cannot be

used for views or functions.

28616 cannot update logical tables INSERTED and DELETED.

28716 triggers are not allowed to use%1.

The 28816 PATINDEX function can only manipulate data types of

char, nchar, varchar, nvarchar, text and ntext.

Invalid property specified for 29116 CAST or CONVERT: for

type''%1!! '

29216, the result space is insufficient, can not convert

smallmoney value to%1!.

29316 cannot convert char value to smallmoney. The syntax of

the char value is incorrect.

29416 smallmoney overflow error caused by the conversion from

char data type to smallmoney data type.

29516 syntax errors from string to smalldatetime data type.

29616 conversion from char data type to smalldatetime data type

leads to smalldatetime value cross boundary.

29816 smalldatetime overflow error caused by the conversion

from datetime data type to smalldatetime data type.

29916 call the function DATEADD with the wrong type%1.

The 30116 query contains an outer join request that is not

allowed.

30316 table''%1!! 'is the internal member of the external join

clause. This is not allowed if the table is also included in

the normal join clause.

30616 cannot compare or sort text, ntext, and image data types

unless IS NULL or LIKE operators are used.

The index ID%1 on the table''%2!! 'specified in the 30716 FROM

clause does not exist.

The index''%1!! 'on the table''%3!!' specified in the 30816

FROM clause does not exist.

31116 cannot use text, ntext or image columns in the inserted

table and the deleted table.

31216 cannot refer to text, ntext, or image columns in the

filter stored procedure.

31316 the number of parameters provided for the process or

function%1! Is not enough.

40116 statement or expression%1! Not yet implemented.

40316 for data types, operators are invalid. The operator is%1!

The type is%2!.

40916%1! Operation cannot use%2! Data type as parameter.

41020 sorting according to the list does not exist in the

first%1! Section COMPUTE clause%2!''BY''expression.

41120 select the aggregate expression COMPUTE%2 without the

existence of the%1 clause in the list.

The 42016 text, ntext, and image data types cannot be used in

the ORDER BY clause.

42516 the data type%1 of the received variable is not equal to

the data type%2 of column''%3'!.

42616 the length of the receive variable%1! Less than the length

of column''%3!! '%2!.

42720 failed to load sysprocedures entries in database ID%2!

Constraint ID%1.

42820 failed to find the row corresponding to the constraint

ID%1 in the database ID%2! In sysconstraints.

42920 compile failed to find new constraint ID%1 in the database

ID%2! Sysconstraints!.

43020 cannot parse the table name of object ID%1 in database

ID%2 when compiling foreign key.

43119 failed to bind foreign key constraints. There are too many

tables involved in the query.

43320 failed to find the CHECK constraint of''%1 '', although

the table is marked as having CHECK constraints.

43620 failed to open the referenced table ID%1 in database

ID%2!.

43720 failed to parse referenced column names in table ID%1.

43820 failed to parse reference column names in table ID%1.

43920 failed to find the FOREIGN KEY constraint of table''%1

KEY 'in table ID%3!', although the table is marked as having

FOREIGN constraints.

44116 cannot use the''%1! 'function on the remote data source.

44316 incorrect use of''%1!! 'in the function.

44416 the SELECT statement contained in the function cannot

return data to the client.

44516 cannot use the COLLATE clause for an expression

containing a COLLATE clause.

44616 can't solve the collation conflict of%1! Operation.

44716 expression type%1! Invalid for the COLLATE clause.

44816 rule''%1 '' invalid.

The 44916 collation conflicts because the sorting clause uses

different sorting rules''%1!! 'and'''%3! ''.

45016 does not support code page conversion for text data types.

From:%d to:%1!.

45116 cannot resolve the collation conflict of

(in%2! Statement).

The 45216 COLLATE clause cannot be used to define user data

types.

45316 supports sorting rule''%1 '' for Unicode data types, and

cannot set the collation at the database or server level.

The last statement in the 45516 function must be a return

statement.

45616 cannot execute value from%1!

The implicit transformation to%2, because the result ordering

rule is not resolved because of the conflict of collation.

45716 cannot perform the implicit conversion from%1 to%2

because the collation of the value cannot be resolved because

of the conflict of collation.

The 50216 SQL debug interface (SDI) requires that SQL Server

cannot log in with system accounts when it is started as a

service. Please reset the control panel to login with user

account.

50316 unable to connect%2! Send symbolic information to the

debugger on%1. Debugging disabled.

50416 unable to connect to the debugger on%1! (error = 0x%2!).

Make sure that the client components have been installed and

registered on%3! (such as ). Debugging of

connection%5! Has been disabled.

50516 the current user account is invoked with SETUSER.

Database is not allowed.

An invalid escape symbol''%1!! 'is specified in the 50616 LIKE

predicate.

Invalid parameter for 50716 SET ROWCOUNT. Must be nonempty and

nonnegative integers.

50816 unable to connect to the debugger on%1! (error = 0x%2!).

Make sure that the client components have been installed and

registered on%3! (such as ). Debugging of

connection%5! Has been disabled.

50911 not found username''%1! ''.

51016 cannot create a worksheet row that is larger than the

allowed maximum. Please resubmit queries with ROBUST PLAN

prompt.

51116 cannot create a row of size%1. This value is greater than

the allowed maximum%2!.

The 51216 subquery returns more than one value. When the query,

followed by = =,! < < = > > =,,,, or as a sub query expression,

this is not allowed.

The insertion or update of the 51316 column conflicts with the

rules enforced by the previous CREATE RULE statement. The

statement has been terminated. The conflict occurred in the

database''%1!! ', table''%3!', column''%5! ''.

51416 cannot connect with debugger on%1! (error = 0x%2!).

Debugging of connection%3! Has been disabled.

51516 cannot insert NULL value into column''%1!! ', table''%3!';

this column does not allow null values. %ls failure.

51616 attempts to initialize the OLE library failed. Please

check the correct version of OLE DLL on this computer.

Overflow occurs when adding value to 51716 column''%1 '.

51816 cannot convert data type%1 to%2!.

52016 SQL Server no longer supports SQL debug interface (SDI)%1!

Version.

52820 detects system errors when attempting to use the upsleep

system function.

52916 explicit conversions from data type%1 to%2 are not

allowed.

53216 timestamp (changed to%1!) indicates that other users have

updated the line.

53516 the difference between the two datetime columns results

in a runtime overflow.

53616 passed the invalid length parameter to the substring

function.

53816 couldn't find''%1!'. The language may have been removed.

Please contact the system administrator.

54216 encountered an invalid datetime value. It's worth more

than 9999 years.

54416 when IDENTITY_INSERT is set to OFF, explicit values

cannot be inserted into the identity column in table''%1 ''.

54516 when IDENTITY_INSERT is set to ON, you must specify the

explicit value of the table''%1.

54716%1! Statement and%2!%3! Constraint''%4!! 'conflict. The

conflict occurred in the database''%6!! ',

table''%8!''%10!%11!%13!.

54816 the replication management scope is full and must be

updated by replication agents. %1! Conflict occurs in

database''%2!! ', table''%4!''%6!%7!%9!. You can call

Sp_adjustpublisheridentityrange to get a new identity range.

55016 attempts to insert or update failed,

The reason is that a view spanned by the target view or the

target view specifies the WITH CHECK OPTION, and that one or

more result lines of the operation do not conform to the

constraints of the CHECK OPTION constraint.

The 55116 checksum has been changed to%1!. This indicates that

other users have updated the line.

The 55215 CryptoAPI function''%1! 'failed. Wrong 0x%2!:%3!

55516 user defined functions are not yet enabled.

55616 because the stored procedure changes the architecture of

the target table, INSERT EXEC fails.

55716 only functions and extended stored procedures can execute

from within the function.

55816 within FUNCTION, remote function calls are not allowed.

56116 access file''%1!! 'failed

56216 access file''%1!! 'failed. You can only access files by

sharing.

The transaction of the 56314 INSERT EXEC statement has been

rolled back. The INSERT EXEC operation will terminate.

56416 attempts to create records with fixed length''%1 ''. The

maximum allowable length is''%2!! ".

56518 server encountered stack overflow during compilation.

56621 write audit tracking error. SQL Server is about to close.

56716 file%1! There is no or not identifiable trace file. Or

error opening the file.

56816 server encountered error''%1!!'.

60112 cannot continue scanning in NOLOCK mode due to data

movement.

60221 failed to find the row corresponding to the index ID%3

in the database ID%1! Object ID%2! In sysindexes. Please run

DBCC CHECKTABLE on sysindexes.

60421 failed to find the row corresponding to the object ID%1

in database''%2 '' in sysobjects. Please run DBCC CHECKTABLE

on sysobjects.

60521 a logical page%1 trying to extract from database''%2 '!

"belongs to object''%4!', not object''%6!! ''.

60721 in the session descriptor of object''%1 "", the space

allocated for search parameters is insufficient. Space with

only%3! Search parameters.

61521 failed to find the database table of ID is%1! Name''%2!!'.

61720 trying to hash the descriptor of the object ID%1! In the

database ID%2!, the descriptor is not found in the hash table.

61821, the VARNO parameter passed to the OpenTable system

function is%1!. The maximum effective value is%2!.

62216 does not assign files for file group''%1 ''. Only when

you add a file, can you fill the table, index, and text, ntext,

and image columns on this file group.

62321 failed to retrieve rows from the page by RID, because the

logical page%1 is not a data page. %2!. %4!.

62421 failed to retrieve rows from the page by RID, because the

requested RID is higher than the last RID value in the

page. %1!. %2!, DBID%3!.

62521 cannot retrieve the row by page RID from page%1, because

slotid (%2!) is invalid.

62616 cannot use ROLLBACK with a save point inside a distributed

transaction.

62716 cannot use SAVE TRANSACTION within a distributed

transaction.

62813 cannot send SAVE TRANSACTION when there is no active

transaction.

63520 process%1! Trying to delete the DES resource lock%2, but

the lock is not controlled by the process.

63720 index shrink program returns invalid state value 0.

63921 failed to extract the logical page%1 of the database ID%2!.

The page is not currently allocated.

"64421 failed to find the index entries of index RID''%1!" in

the index page%3! (index ID%4, database''%5! '').

64921 failed to find the clustered index entry (object ID%2,

status 0x%3!) of page%1. The index page used to search for this

entry is%4 in database''%5!'!

。

650 16在读取或可重复读隔离级别上，只能指定READPAST锁。

651 16不能在表' % 2！”上使用% 1！粒度提示，因为禁止在指定的粒度上进行锁定。

652 16表' % 2！”的索引ID为1！驻留在只读的文件组中，无法更改。

653 20表' % 1！”中同一保管槽的两个缓冲区发生冲突。

654 20没有可供保管表' % 1！”的缓冲区的可用槽。

655 20本应在保管槽中找到表' % 1！”的缓冲区。

666 16表ID为1！的索引ID为2！中，用于重复组的系统生成唯一值超过了最大值除去并重新创建该索引可能会解决该问题；否则可使用其它聚集键。

667 16索引% 1！（属于表' % 2！”驻留在脱机文件组上，无法访问）。

701 19没有足够的系统内存来运行此查询。

708 10警告：由于虚拟内存容量过低，启动过程中已% 1！次使用特殊保留内存。请增加服务器上的虚拟内存。

802 17无法再盗用更多的缓冲区。

804 20在SDES 0x%3 3！为对象' % 4！”所保管的缓冲区池中，未能找到控制逻辑页% 2！的缓冲区0x%3 1！。

809 20在PSS（进程状态结构）中的分配缓冲区池中，不存在数据库' % 3！”中的缓冲区0x%3 1！（分配页% 2！请与技术支持联系）。

813 20已对数据库ID为2！中的逻辑页% 1！进行了哈希运算。

816 20进程ID为1！试图删除缓冲区资源锁% 2！，但在SDES % 3！中，该锁并非由该进程控制。请与技术支持联系。

818 19在SDES % 2！中没有用于控制缓冲区资源锁% 1！的空间。请与技术支持联系。

821 20未能对位于0x%3 1！、缓冲区页号为% 2！、数据库ID为% 3！、设置了散列状态的缓冲区进行解哈希运算。没有找到该缓冲区。% 4！。

822 21未能为请求% 1！启动我/ O.

823 24在文件' % 4！”的偏移量% 3！处的% 2！过程中，检测到I/O错误% 1！。

834 21对脏缓冲区（页% 1！，% 2！% 3！，objId % 4！，sstat % 5！调用了系统函数bufclean）。

840 17设备' % 1！”（物理名称' % 3！”，虚拟设备号% 5！不可用请与系统管理员联系以寻求协助）。

844 10等待缓冲区闩锁时发生超时，类型% 1！，英国石油公司% 2！，页% 3！，% 4！，对象ID为5！：% 6！：% 7！8、时间！将继续等待。

845 17等待缓冲区闩锁时发生超时，类型% 1！，用于页% 2！，数据库ID为3！。

901 21对数据库ID为1！中对象ID为2！的描述符进行了哈希运算后，未能在哈希表中找到该描述符。

902 16若要更改% 1！，数据库就必须处于可执行检查点的状态。

903 22未能在sysindexes中找到数据库ID为2！中系统目录% 1！上的聚集索引所对应的行。这一索引应存在于所有数据库中请对该数据库中的sysindexes运行DBCC CHECKTABLE。

906 22未能在sysobjects中找到数据库' % 3！”中系统目录' % 1！”所对应的行。该系统目录应该存在于所有的数据库中请对该数据库中的sysobjects运行DBCC CHECKTABLE。

911 16未能在数据库“% 1！”的sysdatabases中找到条目。未找到具有该名称的条目。请确保正确地输入了名称。

913 22未能找到ID为% 1！

Database. Perhaps the database is not active or may be in the

process of conversion.

91614 server user''%1! 'is not a valid user in database''%3!'.

92114 database''%1! 'has not been restored. Please try again

later.

92214 restoring database''%1! ''. Please wait for the recovery

operation to complete.

The 92314 database''%1!! 'is in restricted mode. Only the owner

of the database and members of the dbcreator or sysadmin role

can access the database.

The 92414 database''%1!! 'has been opened and only one user can

be available at the same time.

92519 has exceeded the maximum number of databases available

for each query. The maximum allowed is%1!.

92614 cannot open database''%1! ''. The recovery operation has

marked the database as SUSPECT. For more information, see the

SQL Server error log.

92714 cannot open database''%1! ''. The database is in the

middle of the restore operation.

92920 attempts to close the database that has not been opened

yet. Please contact technical support.

94114 cannot open database''%1! ''. The database has not been

upgraded to the latest format.

94214 cannot open the database due to offline database''%1 ''

offline.

94314 cannot open database''%1 '' because the version of the

database (%3!) is later than the current server version (%4!).

94410 is converting database''%1. "" from version%3 to

current version%4!.

94516 because the file is not accessible, or memory or disk

space is insufficient, it can not open the database''%1!!'. For

more information, see the SQL Server error log.

94614 cannot open database''%1. "(version%3!). Please

upgrade this database to the latest version.

94716 error while closing database''%1. '' cleanly.

94814 cannot upgrade database''%1! ''. The version of the

database is%3, and this server supports a version of%4!.

94916 has skipped tempdb. Unable to run queries requiring

tempdb

95014 cannot upgrade database''%1! '- Database Version (%3!)

earlier than SQL Server 7 (%4!).

95110 database''%1!! 'is running from version%3! To version%4!

Upgrade steps.

The 95216 database''%1!! 'is in the transition state. Please

try the statement later.

95316 warning: the index''%1! 'on''%2'!! 'on database''%3!'

may be damaged because the expression assignment has changed

in this version. Removing and recreating indexes.