-
SQL 数据库客户端应用程序的 SQL 错误代码:数据
您现在访问的是微软AZURE全球版技术文档网站,若需要访问由世纪互联运营的MICROSOFT AZURE中国区技术文档网站,请访问 https://docs.azure.cn.
本文列出了 SQL 数据库客户端应用程序的 SQL 错误代码,包括数据库连接错误、暂时性错误(也称为暂时性故障)、资源调控错误、数据库复制问题、弹性池和其他错误。This article lists SQL error codes for SQL Database client applications, including database connection errors, transient errors (also called transient faults), resource governance errors, database copy issues, elastic pool, and other errors. 大多数类别特定于 Azure SQL 数据库,并不适用于 Microsoft SQL Server。Most categories are particular to Azure SQL Database, and do not apply to Microsoft SQL Server. 另请参阅系统错误消息。See also system error messages.
下表涵盖了应用程序尝试访问 SQL 数据库时,可能遇到的连接丢失错误和其他暂时性错误的 SQL 错误代码。The following table covers the SQL error codes for connection loss errors, and other transient errors you might encounter when your application attempts to access SQL Database. 有关如何连接到 Azure SQL 数据库的入门教程,请参阅连接到 Azure SQL 数据库。For getting started tutorials on how to connect to Azure SQL Database, see Connecting to Azure SQL Database.
Azure 基础结构能够在 SQL 数据库服务中出现大量工作负荷时动态地重新配置服务器。The Azure infrastructure has the ability to dynamically reconfigure servers when heavy workloads arise in the SQL Database service. 此动态行为可能会导致客户端程序失去其与 SQL 数据库的连接。This dynamic behavior might cause your client program to lose its connection to SQL Database. 此类错误情况称为暂时性故障。This kind of error condition is called a .
强烈建议客户端程序包含重试逻辑,以便它可以提供一段时间来让暂时性故障纠正自身,并尝试重建连接。It is strongly recommended that your client program has retry logic so that it could reestablish a connection after giving the transient fault time to correct itself. 我们建议在第一次重试前延迟 5 秒钟。We recommend that you delay for 5 seconds before your first retry. 如果在少于 5 秒的延迟后重试,云服务有超载的风险。Retrying after a delay shorter than 5 seconds risks overwhelming the cloud service. 对于后续的每次重试,延迟应以指数级增大,最大值为 60 秒。For each subsequent retry the delay should grow exponentially, up to a maximum of 60 seconds.
出现暂时性故障错误时,客户端程序通常会发出以下错误消息之一:Transient fault errors typically manifest as one of the following error messages from your client programs:
有关重试逻辑的代码示例,请参阅:For code examples of retry logic, see:
SQL Server 连接池 (ADO.NET) 中提供了有关使用 ADO.NET 的客户端的阻塞期的说明。A discussion of the for clients that use ADO.NET is available in SQL Server Connection Pooling (ADO.NET).
以下错误为暂时性错误,并且应在应用程序逻辑中重试:The following errors are transient, and should be retried in application logic:
错误代码Error code | SeveritySeverity | DescriptionDescription |
---|---|---|
40604060 | 1616 | 无法打开该登录请求的数据库“%.*ls”。Cannot open database "%.*ls" requested by the login. 登录失败。The login failed. |
4019740197 | 1717 | 该服务在处理请求时遇到错误。The service has encountered an error processing your request. 请重试。Please try again. 错误代码 %d。Error code %d.当服务由于软件或硬件升级、硬件故障或任何其他故障转移问题而关闭时,将收到此错误。You receive this error when the service is down due to software or hardware upgrades, hardware failures, or any other failover problems. 错误 40197 的消息中嵌入的错误代码 (%d) 提供有关所发生的故障或故障转移类型的其他信息。The error code (%d) embedded within the message of error 40197 provides additional information about the kind of failure or failover that occurred. 错误 40197 的消息中嵌入的错误代码的一些示例有 40020、40143、40166 和 40540。Some examples of the error codes are embedded within the message of error 40197 are 40020, 40143, 40166, and 40540.重新连接到 SQL 数据库服务器会将你自动连接到数据库的正常运行副本。Reconnecting to your SQL Database server automatically connects you to a healthy copy of your database. 应用程序必须捕获错误 40197、记录该消息中嵌入的错误代码 (%d) 以供进行故障排除,并尝试重新连接到 SQL 数据库,直到资源可用且再次建立连接为止。Your application must catch error 40197, log the embedded error code (%d) within the message for troubleshooting, and try reconnecting to SQL Database until the resources are available, and your connection is established again. |
4050140501 | 2020 | 服务当前正忙。The service is currently busy. 请在 10 秒钟后重试请求。Retry the request after 10 seconds. 事件 ID:%ls。Incident ID: %ls. 代码:%d。Code: %d.有关详细信息,请参阅:For more information, see:• Azure SQL 数据库资源限制。• Azure SQL Database resource limits. |
4061340613 | 1717 | 数据库“%.*ls”(在服务器“%.*ls”上)当前不可用。Database '%.*ls' on server '%.*ls' is not currently available. 请稍后重试连接。Please retry the connection later. 如果问题仍然存在,请与客户支持人员联系,并向其提供“%.*ls”的会话追踪 ID。If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'. |
4991849918 | 1616 | 无法处理请求。Cannot process request. 没有足够的资源来处理请求。Not enough resources to process request.服务当前正忙。The service is currently busy. 请稍后重试请求。Please retry the request later. |
4991949919 | 1616 | 无法处理创建或更新请求。Cannot process create or update request. 订阅“%ld”有太多创建或更新操作正在进行。Too many create or update operations in progress for subscription "%ld".服务正忙于为订阅或服务器处理多个创建或更新请求。The service is busy processing multiple create or update requests for your subscription or server. 为了优化资源,当前阻止了请求。Requests are currently blocked for resource optimization. 请查询 sys.dm_operation_status 以了解挂起的操作。Query sys.dm_operation_status for pending operations. 请等到挂起的创建或更新请求完成后,或删除其中一个挂起的请求,再重试请求。Wait until pending create or update requests are complete or delete one of your pending requests and retry your request later. |
4992049920 | 1616 | 无法处理请求。Cannot process request. 订阅“%ld”有太多操作正在进行。Too many operations in progress for subscription "%ld".服务正忙于为此订阅处理多个请求。The service is busy processing multiple requests for this subscription. 为了优化资源,当前阻止了请求。Requests are currently blocked for resource optimization. 请查询 sys.dm_operation_status 以了解操作状态。Query sys.dm_operation_status for operation status. 请等到挂起的请求完成,或删除其中一个挂起的请求,并重试请求。Wait until pending requests are complete or delete one of your pending requests and retry your request later. |
42214221 | 1616 | 由于等待“HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING”的时间过长,登录以读取次要副本失败。Login to read-secondary failed due to long wait on 'HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING'. 副本不可用于登录,因为回收副本时缺少正在进行中的事务的行版本。The replica is not available for login because row versions are missing for transactions that were in-flight when the replica was recycled. 可以通过回滚或提交主要副本上的活动事务来解决此问题。The issue can be resolved by rolling back or committing the active transactions on the primary replica. 通过避免在主要副本上长时间写入事务,可以将此状况的发生次数降到最低。Occurrences of this condition can be minimized by avoiding long write transactions on the primary. |
在 Azure SQL 数据库中复制数据库时,可能会发生以下错误。The following errors can be encountered while copying a database in Azure SQL Database. 有关详细信息,请参阅复制 Azure SQL 数据库。For more information, see Copy an Azure SQL Database.
错误代码Error code | SeveritySeverity | DescriptionDescription |
---|---|---|
4063540635 | 1616 | IP 地址为“%.*ls”的客户端已暂时禁用。Client with IP address '%.*ls' is temporarily disabled. |
4063740637 | 1616 | 创建数据库副本当前处于禁用状态。Create database copy is currently disabled. |
4056140561 | 1616 | 数据库复制失败。Database copy failed. 源数据库或目标数据库不存在。Either the source or target database does not exist. |
4056240562 | 1616 | 数据库复制失败。Database copy failed. 源数据库已删除。The source database has been dropped. |
4056340563 | 1616 | 数据库复制失败。Database copy failed. 目标数据库已删除。The target database has been dropped. |
4056440564 | 1616 | 数据库复制由于内部错误而失败。Database copy failed due to an internal error. 请删除目标数据库,并重试。Please drop target database and try again. |
4056540565 | 1616 | 数据库复制失败。Database copy failed. 不允许来自同一源的多个并发数据库复制。No more than 1 concurrent database copy from the same source is allowed. 请删除目标数据库,并重试。Please drop target database and try again later. |
4056640566 | 1616 | 数据库复制由于内部错误而失败。Database copy failed due to an internal error. 请删除目标数据库,并重试。Please drop target database and try again. |
4056740567 | 1616 | 数据库复制由于内部错误而失败。Database copy failed due to an internal error. 请删除目标数据库,并重试。Please drop target database and try again. |
4056840568 | 1616 | 数据库复制失败。Database copy failed. 源数据库已变得不可用。Source database has become unavailable. 请删除目标数据库,并重试。Please drop target database and try again. |
4056940569 | 1616 | 数据库复制失败。Database copy failed. 目标数据库已变得不可用。Target database has become unavailable. 请删除目标数据库,并重试。Please drop target database and try again. |
4057040570 | 1616 | 数据库复制由于内部错误而失败。Database copy failed due to an internal error. 请删除目标数据库,并重试。Please drop target database and try again later. |
4057140571 | 1616 | 数据库复制由于内部错误而失败。Database copy failed due to an internal error. 请删除目标数据库,并重试。Please drop target database and try again later. |
使用 Azure SQL 数据库时过度使用资源会造成以下错误。The following errors are caused by excessive use of resources while working with Azure SQL Database. 例如:For example:
相关主题:Related topics:
错误代码Error code | SeveritySeverity | DescriptionDescription |
---|---|---|
1092810928 | 2020 | 资源 ID:%d。Resource ID: %d. 数据库的 %s 限制是 %d 且已达到该限制。The %s limit for the database is %d and has been reached. 有关详细信息,请参阅 http://go.microsoft.com/fwlink/?LinkId=267637。For more information, see http://go.microsoft.com/fwlink/?LinkId=267637.资源 ID 指示已达到限制的资源。The Resource ID indicates the resource that has reached the limit. 对于工作线程,资源 ID = 1。For worker threads, the Resource ID = 1. 对于会话,资源 ID = 2。For sessions, the Resource ID = 2.有关此错误以及如何解决此错误的详细信息,请参阅:For more information about this error and how to resolve it, see:• Azure SQL 数据库资源限制。• Azure SQL Database resource limits. |
1092910929 | 2020 | 资源 ID:%d。Resource ID: %d. %s 最小保证为 %d,最大限制为 %d,数据库的当前使用率为 %d。The %s minimum guarantee is %d, maximum limit is %d, and the current usage for the database is %d. 但是,服务器当前太忙,无法支持针对该数据库的数目大于 %d 的请求。However, the server is currently too busy to support requests greater than %d for this database. 有关详细信息,请参阅 http://go.microsoft.com/fwlink/?LinkId=267637。For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. 否则,请稍后重试。Otherwise, please try again later.资源 ID 指示已达到限制的资源。The Resource ID indicates the resource that has reached the limit. 对于工作线程,资源 ID = 1。For worker threads, the Resource ID = 1. 对于会话,资源 ID = 2。For sessions, the Resource ID = 2.有关此错误以及如何解决此错误的详细信息,请参阅:For more information about this error and how to resolve it, see:• Azure SQL 数据库资源限制。• Azure SQL Database resource limits. |
4054440544 | 2020 | 数据库已达到大小配额。The database has reached its size quota. 请将数据分区或删除、删除索引或查阅文档以找到可能的解决方案。Partition or delete data, drop indexes, or consult the documentation for possible resolutions. |
4054940549 | 1616 | 由于有长时间运行的事务,已终止会话。Session is terminated because you have a long-running transaction. 请尝试缩短事务运行时间。Try shortening your transaction. |
4055040550 | 1616 | 由于会话获取的锁过多,已终止该会话。The session has been terminated because it has acquired too many locks. 请尝试在单个事务中读取或修改更少的行。Try reading or modifying fewer rows in a single transaction. |
4055140551 | 1616 | 由于过度使用 TEMPDB,已终止该会话。The session has been terminated because of excessive usage. 请尝试修改查询以减少使用临时表空间。Try modifying your query to reduce the temporary table space usage.如果在使用临时对象,则通过在会话不再需要临时对象后删除这些临时对象,可以节省 TEMPDB 数据库中的空间。If you are using temporary objects, conserve space in the database by dropping temporary objects after they are no longer needed by the session. |
4055240552 | 1616 | 由于过度使用事务日志空间,已终止该会话。The session has been terminated because of excessive transaction log space usage. 请尝试在单个事务中修改更少的行。Try modifying fewer rows in a single transaction.如果在使用 bcp.exe 实用程序或 System.Data.SqlClient.SqlBulkCopy 类执行大容量插入,则可尝试使用 -b batchsize 或 BatchSize 选项来限制在各事务中复制到服务器的行数。If you perform bulk inserts using the utility or the class, try using the or options to limit the number of rows copied to the server in each transaction. 如果正在使用 ALTER INDEX 语句重新生成索引,请尝试使用 REBUILD WITH ONLINE = ON 选项。If you are rebuilding an index with the statement, try using the option. |
4055340553 | 1616 | 由于过度使用内存,已终止该会话。The session has been terminated because of excessive memory usage. 请尝试修改查询以处理更少的行。Try modifying your query to process fewer rows.在 Transact-SQL 代码中减少 ORDER BY 和 GROUP BY 操作的数目可以降低查询的内存需求。Reducing the number of and operations in your Transact-SQL code reduces the memory requirements of your query. |
以下错误与创建和使用弹性池有关:The following errors are related to creating and using elastic pools:
ErrorNumberErrorNumber | ErrorSeverityErrorSeverity | ErrorFormatErrorFormat | ErrorInsertsErrorInserts | ErrorCauseErrorCause | ErrorCorrectiveActionErrorCorrectiveAction |
---|---|---|---|---|---|
11321132 | EX_RESOURCEEX_RESOURCE | 弹性池已达到其存储限制。The elastic pool has reached its storage limit. 弹性池的存储使用不能超过 (%d) MB。The storage usage for the elastic pool cannot exceed (%d) MBs. | 弹性池空间限制 (MB)。Elastic pool space limit in MBs. | 达到弹性池的存储限制时,尝试向数据库写入数据。Attempting to write data to a database when the storage limit of the elastic pool has been reached. | 在可能的情况下,考虑增加弹性池的 DTU 数并/或将存储添加到弹性池,以便提高其存储限制、减少弹性池中各数据库使用的存储,或者从弹性池中删除数据库。Consider increasing the DTUs of and/or adding storage to the elastic pool if possible in order to increase its storage limit, reduce the storage used by individual databases within the elastic pool, or remove databases from the elastic pool. |
1092910929 | EX_USEREX_USER | %s 最小保证为 %d,最大限制为 %d,数据库的当前使用率为 %d。The %s minimum guarantee is %d, maximum limit is %d, and the current usage for the database is %d. 但是,服务器当前太忙,无法支持针对该数据库的数目大于 %d 的请求。However, the server is currently too busy to support requests greater than %d for this database. 请参阅 http://go.microsoft.com/fwlink/?LinkId=267637 以获取帮助。See http://go.microsoft.com/fwlink/?LinkId=267637 for assistance. 否则,请稍后重试。Otherwise, please try again later. | 每个数据库的 DTU/vCore 最小值;每个数据库的 DTU/vCore 最大值DTU / vCore min per database; DTU / vCore max per database | 弹性池中所有数据库上尝试的并发辅助进程(请求)总数超过池限制。The total number of concurrent workers (requests) across all databases in the elastic pool attempted to exceed the pool limit. | 在可能的情况下,考虑增加弹性池的 DTU 数或 vCores 数,以便提高其辅助角色限制,或者从弹性池中删除数据库。Consider increasing the DTUs or vCores of the elastic pool if possible in order to increase its worker limit, or remove databases from the elastic pool. |
4084440844 | EX_USEREX_USER | 弹性池中数据库“%ls”(位于服务器“%ls”上)是“%ls”版本的数据库,不能有连续的复制关系。Database '%ls' on Server '%ls' is a '%ls' edition database in an elastic pool and cannot have a continuous copy relationship. | 数据库名称、数据库版本、服务器名称database name, database edition, server name | 针对弹性池中非高级数据库发出 StartDatabaseCopy 命令。A StartDatabaseCopy command is issued for a non-premium db in an elastic pool. | 即将支持Coming soon |
4085740857 | EX_USEREX_USER | 找不到服务器“%ls”的弹性池,弹性池名称:“%ls”。Elastic pool not found for server: '%ls', elastic pool name: '%ls'. | 服务器名称;弹性池名称name of server; elastic pool name | 指定的弹性池在指定的服务器中不存在。Specified elastic pool does not exist in the specified server. | 提供有效的弹性池名称。Provide a valid elastic pool name. |
4085840858 | EX_USEREX_USER | 弹性池“%ls”已存在于服务器“%ls”中Elastic pool '%ls' already exists in server: '%ls' | 弹性池名称、服务器名称elastic pool name, server name | 指定的弹性池已存在于指定的逻辑服务器中。Specified elastic pool already exists in the specified logical server. | 提供新弹性池名称。Provide new elastic pool name. |
4085940859 | EX_USEREX_USER | 弹性池不支持服务层“%ls”。Elastic pool does not support service tier '%ls'. | 弹性池服务层elastic pool service tier | 进行弹性池预配时,不支持指定服务层。Specified service tier is not supported for elastic pool provisioning. | 提供正确的版本,或者将服务层留空以使用默认服务层。Provide the correct edition or leave service tier blank to use the default service tier. |
4086040860 | EX_USEREX_USER | 弹性池“%ls”和服务目标“%ls”的组合无效。Elastic pool '%ls' and service objective '%ls' combination is invalid. | 弹性池名称;服务层elastic pool name; service tier | 仅当资源类型指定为“ElasticPool”时,才能一起指定弹性池和服务层。Elastic pool and service tier can be specified together only if resource type is specified as 'ElasticPool'. | 指定正确的弹性池和服务层组合。Specify correct combination of elastic pool and service tier. |
4086140861 | EX_USEREX_USER | 数据库版本“%.ls”必须与弹性池服务层“%. ls”相同。The database edition '%. ls'. | 数据库版本、弹性池服务层database edition, elastic pool service tier | 数据库版本不同于弹性池服务层。The database edition is different than the elastic pool service tier. | 请勿指定不同于弹性池服务层的数据库版本。Do not specify a database edition which is different than the elastic pool service tier. 请注意,数据库版本不需要指定。Note that the database edition does not need to be specified. |
4086240862 | EX_USEREX_USER | 如果指定了弹性池服务目标,则必须指定弹性池名称。Elastic pool name must be specified if the elastic pool service objective is specified. | 无None | 弹性池服务目标没有唯一地标识弹性池。Elastic pool service objective does not uniquely identify an elastic pool. | 如果使用弹性池服务目标,则指定弹性池名称。Specify the elastic pool name if using the elastic pool service objective. |
4086440864 | EX_USEREX_USER | 对于服务层“%.*ls”来说,弹性池的 DTU 数必须至少为 (%d) 个 DTU。The DTUs for the elastic pool must be at least (%d) DTUs for service tier '%.*ls'. | 弹性池的 DTU 数;弹性池服务层。DTUs for elastic pool; elastic pool service tier. | 尝试将弹性池的 DTU 数设置为最小限制以下。Attempting to set the DTUs for the elastic pool below the minimum limit. | 重新尝试将弹性池的 DTU 数至少设置为最小限制。Retry setting the DTUs for the elastic pool to at least the minimum limit. |
4086540865 | EX_USEREX_USER | 对于服务层“%.*ls”来说,弹性池的 DTU 数不能超过 (%d) 个 DTU。The DTUs for the elastic pool cannot exceed (%d) DTUs for service tier '%.*ls'. | 弹性池的 DTU 数;弹性池服务层。DTUs for elastic pool; elastic pool service tier. | 尝试将弹性池的 DTU 数设置为高出最大限制。Attempting to set the DTUs for the elastic pool above the maximum limit. | 重新尝试将弹性池的 DTU 数设置为不超过最大限制。Retry setting the DTUs for the elastic pool to no greater than the maximum limit. |
4086740867 | EX_USEREX_USER | 对于服务层“%.*ls”来说,每个数据库的 DTU 最大值必须至少为 (%d)。The DTU max per database must be at least (%d) for service tier '%.*ls'. | 每个数据库的 DTU 最大值;弹性池服务层DTU max per database; elastic pool service tier | 尝试将每个数据库的 DTU 最大值设置为低于支持的限制。Attempting to set the DTU max per database below the supported limit. | 考虑使用支持所需设置的弹性池服务层。Consider using the elastic pool service tier that supports the desired setting. |
4086840868 | EX_USEREX_USER | 对于服务层“%.*ls”来说,每个数据库的 DTU 最大值不能超过 (%d)。The DTU max per database cannot exceed (%d) for service tier '%.*ls'. | 每个数据库的 DTU 最大值;弹性池服务层。DTU max per database; elastic pool service tier. | 尝试将每个数据库的 DTU 最大值设置为超出支持的限制。Attempting to set the DTU max per database beyond the supported limit. | 考虑使用支持所需设置的弹性池服务层。Consider using the elastic pool service tier that supports the desired setting. |
4087040870 | EX_USEREX_USER | 对于服务层“%.*ls”来说,每个数据库的 DTU 最小值不能超过 (%d)。The DTU min per database cannot exceed (%d) for service tier '%.*ls'. | 每个数据库的 DTU 最小值;弹性池服务层。DTU min per database; elastic pool service tier. | 尝试将每个数据库的 DTU 最小值设置为超出支持的限制。Attempting to set the DTU min per database beyond the supported limit. | 考虑使用支持所需设置的弹性池服务层。Consider using the elastic pool service tier that supports the desired setting. |
4087340873 | EX_USEREX_USER | 数据库数目 (%d) 和每个数据库的 DTU 最小值 (%d) 不能超过弹性池的 DTU 数 (%d)。The number of databases (%d) and DTU min per database (%d) cannot exceed the DTUs of the elastic pool (%d). | 弹性池中的数据库数;每个数据库的 DTU 最小值;弹性池的 DTU 数。Number databases in elastic pool; DTU min per database; DTUs of elastic pool. | 尝试指定弹性池中数据库的 DTU 最小值,该最小值超出弹性池的 DTU 数。Attempting to specify DTU min for databases in the elastic pool that exceeds the DTUs of the elastic pool. | 考虑增加弹性池的 DTU 数,或者降低每个数据库的 DTU 最小值,或者降低弹性池中数据库的数目。Consider increasing the DTUs of the elastic pool, or decrease the DTU min per database, or decrease the number of databases in the elastic pool. |
4087740877 | EX_USEREX_USER | 除非弹性池不含任何数据库,否则不能将其删除。An elastic pool cannot be deleted unless it does not contain any databases. | 无None | 弹性池包含一个或多个数据库,因此无法将其删除。The elastic pool contains one or more databases and therefore cannot be deleted. | 删除弹性池中的数据库,以便删除弹性池。Remove databases from the elastic pool in order to delete it. |
4088140881 | EX_USEREX_USER | 弹性池“%.*ls”已达到其数据库计数限制。The elastic pool '%.*ls' has reached its database count limit. 对于 DTU 数为 (%d) 的弹性池,弹性池的数据库计数限制不能超出 (%d)。The database count limit for the elastic pool cannot exceed (%d) for an elastic pool with (%d) DTUs. | 弹性池的名称;弹性池的数据库计数限制;资源池的 eDTU 数。Name of elastic pool; database count limit of elastic pool; eDTUs for resource pool. | 达到弹性池的数据库计数限制时,尝试创建数据库或将其添加到弹性池。Attempting to create or add database to elastic pool when the database count limit of the elastic pool has been reached. | 在可能的情况下,考虑增加弹性池的 DTU 数,以便提高其数据库限制,或者从弹性池中删除数据库。Consider increasing the DTUs of the elastic pool if possible in order to increase its database limit, or remove databases from the elastic pool. |
4088940889 | EX_USEREX_USER | 弹性池“%.*ls”的 DTU 数或存储限制不能降低,因为这样就无法为其数据库提供足够的存储空间。The DTUs or storage limit for the elastic pool '%.*ls' cannot be decreased since that would not provide sufficient storage space for its databases. | 弹性池的名称。Name of elastic pool. | 尝试将弹性池的存储限制降低到其存储使用量以下。Attempting to decrease the storage limit of the elastic pool below its storage usage. | 考虑降低弹性池中各个数据库的存储使用量,或者从池中删除数据库以降低其 DTU 数或存储限制。Consider reducing the storage usage of individual databases in the elastic pool or remove databases from the pool in order to reduce its DTUs or storage limit. |
4089140891 | EX_USEREX_USER | 每个数据库的 DTU 最小值 (%d) 不能超过每个数据库的 DTU 最大值 (%d)。The DTU min per database (%d) cannot exceed the DTU max per database (%d). | 每个数据库的 DTU 最小值;每个数据库的 DTU 最大值。DTU min per database; DTU max per database. | 尝试将每个数据库的 DTU 最小值设置为高于每个数据库的 DTU 最大值。Attempting to set the DTU min per database higher than the DTU max per database. | 确保每个数据库的 DTU 最小值不超过每个数据库的 DTU 最大值。Ensure the DTU min per databases does not exceed the DTU max per database. |
TBDTBD | EX_USEREX_USER | 弹性池中单个数据库的存储大小不能超过“%.*ls”服务层弹性池所允许的最大大小。The storage size for an individual database in an elastic pool cannot exceed the max size allowed by '%.*ls' service tier elastic pool. | 弹性池服务层elastic pool service tier | 数据库的最大大小超过弹性池服务层允许的最大大小。The max size for the database exceeds the max size allowed by the elastic pool service tier. | 将数据库的最大大小设置为处于弹性池服务层允许的最大大小限制范围内。Set the max size of the database within the limits of the max size allowed by the elastic pool service tier. |
相关主题:Related topics:
以下错误不属于前面的任何类别。The following errors do not fall into any previous categories.
错误代码Error code | SeveritySeverity | DescriptionDescription |
---|---|---|
1500615006 | 1616 | (AdministratorLogin) 不是有效的名称,因为它包含无效字符。(AdministratorLogin) is not a valid name because it contains invalid characters. |
1845218452 | 1414 | 登录失败。Login failed. 该登录来自不受信任的域,不能用于 Windows 身份验证。%.*ls(此版本的 SQL Server 不支持 Windows 登录。)The login is from an untrusted domain and cannot be used with Windows authentication.%.*ls (Windows logins are not supported in this version of SQL Server.) |
1845618456 | 1414 | 用户“%.*ls”的登录失败。%.*ls%.*ls(用户“%.*ls”的登录失败。Login failed for user '%.*ls'.%.*ls%.*ls(The login failed for user "%.*ls". 密码更改失败。The password change failed. 此版本的 SQL Server 不支持在登录过程中更改密码。)Password change during login is not supported in this version of SQL Server.) |
1847018470 | 1414 | 用户“%.*ls”的登录失败。Login failed for user '%.*ls'. 原因:该帐户已禁用。%.*lsReason: The account is disabled.%.*ls |
4001440014 | 1616 | 不能在同一个事务中使用多个数据库。Multiple databases cannot be used in the same transaction. |
4005440054 | 1616 | 此版本的 SQL Server 不支持没有聚集索引的表。Tables without a clustered index are not supported in this version of SQL Server. 创建聚集索引,然后重试。Create a clustered index and try again. |
4013340133 | 1515 | 此版本的 SQL Server 不支持此操作。This operation is not supported in this version of SQL Server. |
4050640506 | 1616 | 指定的 SID 对此版本的 SQL Server 无效。Specified SID is invalid for this version of SQL Server. |
4050740507 | 1616 | 不能使用此版本的 SQL Server 中的参数调用“%.*ls”。'%.*ls' cannot be invoked with parameters in this version of SQL Server. |
4050840508 | 1616 | USE 语句不支持在数据库间切换。USE statement is not supported to switch between databases. 请使用新连接来连接到其他数据库。Use a new connection to connect to a different database. |
4051040510 | 1616 | 此版本的 SQL Server 不支持语句“%.*ls”Statement '%.*ls' is not supported in this version of SQL Server |
4051140511 | 1616 | 此版本的 SQL Server 不支持内置函数“%.*ls”。Built-in function '%.*ls' is not supported in this version of SQL Server. |
4051240512 | 1616 | 此版本的 SQL Server 不支持已过时的功能“%ls”。Deprecated feature '%ls' is not supported in this version of SQL Server. |
4051340513 | 1616 | 此版本的 SQL Server 不支持服务器变量“%.*ls”。Server variable '%.*ls' is not supported in this version of SQL Server. |
4051440514 | 1616 | 此版本的 SQL Server 不支持“%ls”。'%ls' is not supported in this version of SQL Server. |
4051540515 | 1616 | 此版本的 SQL Server 不支持引用“%.*ls”中的数据库和/或服务器名称。Reference to database and/or server name in '%.*ls' is not supported in this version of SQL Server. |
4051640516 | 1616 | 此版本的 SQL Server 不支持全局临时对象。Global temp objects are not supported in this version of SQL Server. |
4051740517 | 1616 | 此版本的 SQL Server 不支持关键字或语句选项“%.*ls”。Keyword or statement option '%.*ls' is not supported in this version of SQL Server. |
4051840518 | 1616 | 此版本的 SQL Server 不支持 DBCC 命令“%.*ls”。DBCC command '%.*ls' is not supported in this version of SQL Server. |
4052040520 | 1616 | 此版本的 SQL Server 不支持安全对象类“%S_MSG”。Securable class '%S_MSG' not supported in this version of SQL Server. |
4052140521 | 1616 | 此版本的 SQL Server 不支持服务器范围中的安全对象类“%S_MSG”。Securable class '%S_MSG' not supported in the server scope in this version of SQL Server. |
4052240522 | 1616 | 此版本的 SQL Server 不支持数据库主体“%.*ls”类型。Database principal '%.*ls' type is not supported in this version of SQL Server. |
4052340523 | 1616 | 此版本的 SQL Server 不支持创建隐式用户“%.*ls”。Implicit user '%.*ls' creation is not supported in this version of SQL Server. 请在使用该用户前显式创建它。Explicitly create the user before using it. |
4052440524 | 1616 | 此版本的 SQL Server 不支持数据类型“%.*ls”。Data type '%.*ls' is not supported in this version of SQL Server. |
4052540525 | 1616 | 此版本的 SQL Server 不支持 WITH“%.ls”。WITH '%.ls' is not supported in this version of SQL Server. |
4052640526 | 1616 | 此版本的 SQL Server 不支持“%.*ls”行集提供程序。'%.*ls' rowset provider not supported in this version of SQL Server. |
4052740527 | 1616 | 此版本的 SQL Server 不支持链接服务器。Linked servers are not supported in this version of SQL Server. |
4052840528 | 1616 | 此版本的 SQL Server 用户不能映射为证书、非对称密钥或 Windows 登录。Users cannot be mapped to certificates, asymmetric keys, or Windows logins in this version of SQL Server. |
4052940529 | 1616 | 此版本的 SQL Server 不支持模拟上下文中的内置函数“%.*ls”。Built-in function '%.*ls' in impersonation context is not supported in this version of SQL Server. |
4053240532 | 1111 | 无法打开该登录请求的服务器“%.*ls”。Cannot open server "%.*ls" requested by the login. 登录失败。The login failed. |
4055340553 | 1616 | 由于过度使用内存,已终止该会话。The session has been terminated because of excessive memory usage. 请尝试修改查询以处理更少的行。Try modifying your query to process fewer rows. 在 Transact-SQL 代码中减少 ORDER BY 和 GROUP BY 操作的数目有助于降低查询的内存需求。Reducing the number of and operations in your Transact-SQL code helps reduce the memory requirements of your query. |
4060440604 | 1616 | 由于将超过服务器的配额,无法执行 CREATE/ALTER DATABASE。Could not CREATE/ALTER DATABASE because it would exceed the quota of the server. |
4060640606 | 1616 | 此版本的 SQL Server 不支持附加数据库。Attaching databases is not supported in this version of SQL Server. |
4060740607 | 1616 | 此版本的 SQL Server 不支持 Windows 登录。Windows logins are not supported in this version of SQL Server. |
4061140611 | 1616 | 服务器上最多可以定义 128 个防火墙规则。Servers can have at most 128 firewall rules defined. |
4061440614 | 1616 | 防火墙规则的开始 IP 地址不能超过结束 IP 地址。Start IP address of firewall rule cannot exceed End IP address. |
4061540615 | 1616 | 无法打开此登录请求的服务器“{0}”。Cannot open server '{0}' requested by the login. 不允许 IP 地址为“{1}”的客户端访问此服务器。Client with IP address '{1}' is not allowed to access the server.要启用访问,请使用 SQL 数据库门户或在主数据库上运行 sp_set_firewall_rule,以针对此 IP 地址或地址范围创建防火墙规则。To enable access, use the SQL Database Portal or run sp_set_firewall_rule on the master database to create a firewall rule for this IP address or address range. 为使此更改生效,最多可能需要 5 分钟。It may take up to five minutes for this change to take effect. |
4061740617 | 1616 | 以(规则名称)开头的防火墙规则名称过长。The firewall rule name that starts with (rule name) is too long. 最大长度为 128。Maximum length is 128. |
4061840618 | 1616 | 防火墙规则名称不能为空。The firewall rule name cannot be empty. |
4062040620 | 1616 | 用户“%.*ls”的登录失败。The login failed for user "%.*ls". 密码更改失败。The password change failed. 此版本的 SQL Server 不支持在登录过程中更改密码。Password change during login is not supported in this version of SQL Server. |
4062740627 | 2020 | 服务器“{0}”和数据库“{1}”中的操作正在进行。Operation on server '{0}' and database '{1}' is in progress. 请等待几分钟,并重试。Please wait a few minutes before trying again. |
4063040630 | 1616 | 密码验证失败。Password validation failed. 该密码太短,不符合策略要求。The password does not meet policy requirements because it is too short. |
4063140631 | 1616 | 指定的密码过长。The password that you specified is too long. 密码的长度不能超过 128 个字符。The password should have no more than 128 characters. |
4063240632 | 1616 | 密码验证失败。Password validation failed. 该密码不够复杂,不符合策略要求。The password does not meet policy requirements because it is not complex enough. |
4063640636 | 1616 | 无法在此操作中使用保留的数据库名称“%.*ls”。Cannot use a reserved database name '%.*ls' in this operation. |
4063840638 | 1616 | 订阅 ID (subscription-id) 无效。Invalid subscription id (subscription-id). 订阅不存在。Subscription does not exist. |
4063940639 | 1616 | 请求不符合架构:(结构错误)。Request does not conform to schema: (schema error). |
4064040640 | 2020 | 服务器遇到意外的异常。The server encountered an unexpected exception. |
4064140641 | 1616 | 指定的位置无效。The specified location is invalid. |
4064240642 | 1717 | 服务器当前太忙。The server is currently too busy. 请稍后重试。Please try again later. |
4064340643 | 1616 | 指定的 x-ms-version 标头值无效。The specified x-ms-version header value is invalid. |
4064440644 | 1414 | 授权访问指定的订阅失败。Failed to authorize access to the specified subscription. |
4064540645 | 1616 | 服务器名称 (servername) 不能为空或 null。Servername (servername) cannot be empty or null. 它只能由小写字母“a”-“z”、数字 0-9 和连字符组成。It can only be made up of lowercase letters 'a'-'z', the numbers 0-9 and the hyphen. 连字符不能位于名称的开头或结尾。The hyphen may not lead or trail in the name. |
4064640646 | 1616 | 订阅 ID 不能为空。Subscription ID cannot be empty. |
4064740647 | 1616 | 订阅 (subscription-id) 不包含服务器 (servername)。Subscription (subscription-id) does not have server (servername). |
4064840648 | 1717 | 执行了过多请求。Too many requests have been performed. 请稍后重试。Please retry later. |
4064940649 | 1616 | 指定的内容类型无效。Invalid content-type is specified. 仅支持应用程序/xml。Only application/xml is supported. |
4065040650 | 1616 | 订阅 (subscription-id) 不存在或未准备好执行该操作。Subscription (subscription-id) does not exist or is not ready for the operation. |
4065140651 | 1616 | 无法创建服务器,因为订阅 (subscription-id) 已禁用。Failed to create server because the subscription (subscription-id) is disabled. |
4065240652 | 1616 | 无法移动或创建服务器。Cannot move or create server. 订阅 (subscription-id) 将超过服务器配额。Subscription (subscription-id) will exceed server quota. |
4067140671 | 1717 | 网关与管理服务之间的通信失败。Communication failure between the gateway and the management service. 请稍后重试。Please retry later. |
4085240852 | 1616 | 无法在服务器“%.*ls”中打开登录请求的数据库“%.*ls”。Cannot open database '%.*ls' on server '%.*ls' requested by the login. 仅允许使用已启用安全性的连接字符串访问数据库。Access to the database is only allowed using a security-enabled connection string. 要访问此数据库,请将连接字符串修改为在服务器 FQDN 中包含“secure”。也就是说,'server name'.database.windows.net 应修改为 'server name'.databasesecure.windows.net。To access this database, modify your connection strings to contain ‘secure’ in the server FQDN - 'server name'.database.windows.net should be modified to 'server name'.database..windows.net. |
4091440914 | 1616 | 无法打开登录时请求的服务器‘[服务器-名称]’。Cannot open server '' requested by the login. 不允许客户端访问服务器。Client is not allowed to access the server.若要修复,请考虑添加虚拟网络规则。To fix, consider adding a virtual network rule. |
4516845168 | 1616 | SQL Azure 系统负载过小,正在设置单个服务器的并发数据库 CRUD 操作(例如创建数据库)数的上限。The SQL Azure system is under load, and is placing an upper limit on concurrent DB CRUD operations for a single server (e.g., create database). 在错误消息中指定的服务器已超过最大并发连接数。The server specified in the error message has exceeded the maximum number of concurrent connections. 请稍后重试。Try again later. |
4516945169 | 1616 | SQL Azure 系统负载过小,正在设置单个订阅的并发服务器 CRUD 操作(例如创建服务器)数的上限。The SQL azure system is under load, and is placing an upper limit on the number of concurrent server CRUD operations for a single subscription (e.g., create server). 在错误消息中指定的订阅已超过最大并发连接数,已拒绝请求。The subscription specified in the error message has exceeded the maximum number of concurrent connections, and the request was denied. 请稍后重试。Try again later. |
最新更新
nodejs爬虫
Python正则表达式完全指南
爬取豆瓣Top250图书数据
shp 地图文件批量添加字段
爬虫小试牛刀(爬取学校通知公告)
【python基础】函数-初识函数
【python基础】函数-返回值
HTTP请求:requests模块基础使用必知必会
Python初学者友好丨详解参数传递类型
如何有效管理爬虫流量?
SQL SERVER中递归
2个场景实例讲解GaussDB(DWS)基表统计信息估
常用的 SQL Server 关键字及其含义
动手分析SQL Server中的事务中使用的锁
openGauss内核分析:SQL by pass & 经典执行
一招教你如何高效批量导入与更新数据
天天写SQL,这些神奇的特性你知道吗?
openGauss内核分析:执行计划生成
[IM002]Navicat ODBC驱动器管理器 未发现数据
初入Sql Server 之 存储过程的简单使用
这是目前我见过最好的跨域解决方案!
减少回流与重绘
减少回流与重绘
如何使用KrpanoToolJS在浏览器切图
performance.now() 与 Date.now() 对比
一款纯 JS 实现的轻量化图片编辑器
关于开发 VS Code 插件遇到的 workbench.scm.
前端设计模式——观察者模式
前端设计模式——中介者模式
创建型-原型模式