Warning Sorry There Was an Error Processing Your Request Please Try Again Runescape Sign Up

اردیبهشت ۲۶, ۱۴۰۱ ارسال یک نظر

Troubleshooting connectivity problems and other errors with Azure SQL Database and Azure SQL Managed Instance

Article
04/26/2022
32 minutes to read

APPLIES TO: Azure SQL Database Azure SQL Managed Example

Y'all receive error messages when the connection to Azure SQL Database or Azure SQL Managed Example fails. These connexion problems can be caused by reconfiguration, firewall settings, a connexion timeout, wrong login information, or failure to employ best practices and design guidelines during the application design process. Additionally, if the maximum limit on some Azure SQL Database or SQL Managed Instance resources is reached, y'all can no longer connect.

Transient fault error messages (40197, 40613 and others)

The Azure infrastructure has the ability to dynamically reconfigure servers when heavy workloads ascend in the SQL Database service. This dynamic beliefs might crusade your client program to lose its connection to the database or instance. This kind of error condition is called a transient error. Database reconfiguration events occur because of a planned consequence (for example, a software upgrade) or an unplanned effect (for instance, a process crash, or load balancing). Nearly reconfiguration events are by and large brusque-lived and should be completed in less than sixty seconds at well-nigh. However, these events tin occasionally take longer to stop, such as when a large transaction causes a long-running recovery. The following table lists diverse transient errors that applications can receive when connecting to Azure SQL Database.

List of transient fault error codes

Mistake code	Severity	Clarification
926	xiv	Database 'replicatedmaster' cannot be opened. It has been marked SUSPECT by recovery. Run across the SQL Server errorlog for more than information. This mistake may exist logged on SQL Managed Instance errorlog, for a brusk period of fourth dimension, during the terminal stage of a reconfiguration, while the old primary is shutting down its log. Other, non-transient scenarios involving this fault message are described in the MSSQL Errors documentation.
4060	16	Cannot open database "%.*ls" requested by the login. The login failed. For more information, see Errors 4000 to 4999
40197	17	The service has encountered an error processing your request. Please endeavour once again. Error code %d. You receive this error when the service is downward due to software or hardware upgrades, hardware failures, or whatsoever other failover problems. The error lawmaking (%d) embedded within the message of mistake 40197 provides additional information about the kind of failure or failover that occurred. Some examples of the error codes are embedded within the message of fault 40197 are 40020, 40143, 40166, and 40540. Reconnecting automatically connects you to a healthy copy of your database. Your application must catch error 40197, log the embedded mistake code (%d) within the bulletin for troubleshooting, and endeavour reconnecting to SQL Database until the resource are available, and your connexion is established again. For more information, see Transient errors.
40501	xx	The service is currently decorated. Retry the request after 10 seconds. Incident ID: %ls. Lawmaking: %d. For more than information, see: • Logical SQL server resource limits • DTU-based limits for unmarried databases • DTU-based limits for rubberband pools • vCore-based limits for unmarried databases • vCore-based limits for elastic pools • Azure SQL Managed Example resource limits.
40613	17	Database '%.ls' on server '%.ls' is not currently bachelor. Delight retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '%.*ls'. This mistake may occur if at that place is already an existing dedicated administrator connection (DAC) established to the database. For more information, see Transient errors.
49918	16	Cannot process request. Non enough resources to process asking. The service is currently decorated. Please retry the request later. For more information, see: • Logical SQL server resources limits • DTU-based limits for single databases • DTU-based limits for elastic pools • vCore-based limits for single databases • vCore-based limits for rubberband pools • Azure SQL Managed Instance resources limits.
49919	16	Cannot process create or update request. Too many create or update operations in progress for subscription "%ld". The service is decorated processing multiple create or update requests for your subscription or server. Requests are currently blocked for resources optimization. Query sys.dm_operation_status for awaiting operations. Look until awaiting create or update requests are complete or delete one of your pending requests and retry your request later. For more information, see: • Logical SQL server resources limits • DTU-based limits for single databases • DTU-based limits for elastic pools • vCore-based limits for single databases • vCore-based limits for elastic pools • Azure SQL Managed Instance resources limits.
49920	16	Cannot process request. Besides many operations in progress for subscription "%ld". The service is busy processing multiple requests for this subscription. Requests are currently blocked for resource optimization. Query sys.dm_operation_status for operation status. Look until pending requests are consummate or delete one of your awaiting requests and retry your asking later. For more information, see: • Logical SQL server resource limits • DTU-based limits for single databases • DTU-based limits for elastic pools • vCore-based limits for single databases • vCore-based limits for rubberband pools • Azure SQL Managed Instance resource limits.
4221	16	Login to read-secondary failed due to long look on 'HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING'. The replica is not bachelor for login considering row versions are missing for transactions that were in-flight when the replica was recycled. The result can be resolved past 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.
615	21	Could non find database ID %d, proper noun '%.*ls' . Error Lawmaking 615. This means in-retentivity cache is non in-sync with SQL server instance and lookups are retrieving dried database ID. SQL logins use in-memory cache to get the database name to ID mapping. The cache should be in sync with backend database and updated whenever attach and detach of database to/from the SQL server example occurs. You receive this error when detach workflow fail to clean-upwards the in-memory cache on fourth dimension and subsequent lookups to the database point to stale database ID. Try reconnecting to SQL Database until the resources are bachelor, and the connection is established again. For more information, see Transient errors.

Steps to resolve transient connectivity bug

Bank check the Microsoft Azure Service Dashboard for any known outages that occurred during the fourth dimension during which the errors were reported by the application.
Applications that connect to a cloud service such as Azure SQL Database should expect periodic reconfiguration events and implement retry logic to handle these errors instead of surfacing application errors to users.
As a database approaches its resources limits, it can seem to be a transient connectivity result. Come across Resource limits.
If connectivity problems keep, or if the duration for which your awarding encounters the error exceeds 60 seconds or if yous run into multiple occurrences of the error in a given day, file an Azure back up asking by selecting Go Back up on the Azure Back up site.

Implementing Retry Logic

It is strongly recommended that your customer program has retry logic then that information technology could reestablish a connection after giving the transient fault time to correct itself. We recommend that y'all delay for five seconds earlier your start retry. Retrying after a filibuster shorter than v-seconds risks overwhelming the cloud service. For each subsequent retry the filibuster should abound exponentially, up to a maximum of 60 seconds.

For lawmaking examples of retry logic, see:

Connect resiliently to SQL with ADO.NET
Connect resiliently to SQL with PHP

For additional data on handling transient errors in your awarding review Troubleshooting transient connection errors to SQL Database

A discussion of the blocking period for clients that use ADO.NET is bachelor in Connection Pooling (ADO.Cyberspace).

The issue occurs if the awarding tin't connect to the server.

To resolve this issue, endeavour the steps (in the order presented) in the Steps to fix mutual connectedness issues department.

The server/instance was not found or was not attainable (errors 26, twoscore, 10053)

Error 26: Error Locating server specified

System.Data.SqlClient.SqlException: A network-related or example-specific fault occurred while establishing a connection to SQL Server. The server was not plant or was non accessible. Verify that the example proper name is correct and that SQL Server is configured to permit remote connections.(provider: SQL Network Interfaces, error: 26 – Fault Locating Server/Instance Specified)

Error 40: Could not open a connection to the server

A network-related or instance-specific mistake occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connexion to SQL Server)

Mistake 10053: A transport-level error has occurred when receiving results from the server

10053: A ship-level error has occurred when receiving results from the server. (Provider: TCP Provider, error: 0 - An established connection was aborted by the software in your host machine)

These issues occur if the application tin can't connect to the server.

To resolve these issues, try the steps (in the social club presented) in the Steps to fix common connection issues section.

Cannot connect to server due to firewall issues

Error 40615: Cannot connect to < servername >

To resolve this issue, configure firewall settings on SQL Database through the Azure portal.

Fault v: Cannot connect to < servername >

To resolve this effect, brand sure that port 1433 is open up for outbound connections on all firewalls between the client and the internet.

Unable to log in to the server (errors 18456, 40531)

Login failed for user '<User name>'.This session has been assigned a tracing ID of '<Tracing ID>'. Provide this tracing ID to customer back up when you need assist. (Microsoft SQL Server, Error: 18456)

To resolve this event, contact your service administrator to provide you with a valid user name and password.

Typically, the service administrator can use the following steps to add together the login credentials:

Run the following SQL query in the master database to cheque whether the login name is disabled:

                  SELECT proper noun, is_disabled FROM sys.sql_logins;

If the corresponding proper name is disabled, enable it by using the following statement:

                  ALTER LOGIN <User name> ENABLE;

If the SQL login user name doesn't be, edit and run the post-obit SQL query to create a new SQL login:

                  CREATE LOGIN <SQL_login_name, sysname, login_name> WITH PASSWORD = '<password, sysname, Change_Password>'; GO

In SSMS Object Explorer, expand Databases.
Select the database that you want to grant the user permission to.
Right-click Security, and so select New, User.

In the generated script with placeholders (sample shown below), replace template parameters past post-obit the steps hither and execute it:

                  CREATE USER [<user_name, sysname, user_name>] FOR LOGIN [<login_name, sysname, login_name>] WITH DEFAULT_SCHEMA = [<default_schema, sysname, dbo>]; GO  -- Add user to the database possessor role EXEC sp_addrolemember N'db_owner', Due north'<user_name, sysname, user_name>'; GO

You can also utilize sp_addrolemember to map specific users to specific database roles.

Note

In Azure SQL Database, consider the newer ALTER ROLE syntax for managing database role membership.

For more than information, see Managing databases and logins in Azure SQL Database.

Connection timeout expired errors

System.Data.SqlClient.SqlException (0x80131904): Connectedness Timeout Expired

System.Data.SqlClient.SqlException (0x80131904): Connectedness Timeout Expired. The timeout menstruum elapsed while attempting to consume the pre-login handshake acknowledgement. This could exist because the pre-login handshake failed or the server was unable to answer back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=3; handshake=29995;

Arrangement.Information.SqlClient.SqlException (0x80131904): Timeout expired

System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the functioning or the server is not responding.

Arrangement.Data.Entity.Core.EntityException: The underlying provider failed on Open

System.Information.Entity.Cadre.EntityException: The underlying provider failed on Open. -> Organization.Data.SqlClient.SqlException: Timeout expired. The timeout menses elapsed prior to completion of the operation or the server is not responding. -> Arrangement.ComponentModel.Win32Exception: The wait operation timed out

Cannot connect to < server proper name >

Cannot connect to <server name>.ADDITIONAL INFORMATION:Connectedness Timeout Expired. The timeout period elapsed during the mail service-login stage. The connection could have timed out while waiting for server to consummate the login procedure and respond; Or it could take timed out while attempting to create multiple agile connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=231; handshake=983; [Login] initialization=0; hallmark=0; [Mail service-Login] consummate=13000; (Microsoft SQL Server, Error: -2) For help, click: http://get.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476 The wait operation timed out

These exceptions can occur either because of connection or query issues. To confirm that this error is acquired by connectivity issues, see Confirm whether an error is caused by a connectivity outcome.

Connectedness timeouts occur because the application can't connect to the server. To resolve this result, endeavor the steps (in the order presented) in the Steps to set common connection bug section.

Resources governance errors

Azure SQL Database uses a resource governance implementation based on Resource Governor to enforce resource limits. Larn more than nigh resource management in Azure SQL Database.

The near mutual resource governance errors are listed first with details, followed past a table of resource governance fault messages.

Error 10928: Resource ID : one. The asking limit for the database is %d and has been reached.

The detailed error message in this case reads: Resource ID : one. The request limit for the database is %d and has been reached. See 'http://get.microsoft.com/fwlink/?LinkId=267637' for assistance.

This error message indicates that the worker limit for Azure SQL Database has been reached. A value will be present instead of the placeholder %d. This value indicates the worker limit for your database at the time the limit was reached.

Note

The initial offering of Azure SQL Database supported just unmarried threaded queries. At that time, the number of requests was always equivalent to the number of workers. Mistake message 10928 in Azure SQL Database contains the wording "The request limit for the database is N and has been reached" for backwards compatibility purposes. The limit reached is really the number of workers. If your max degree of parallelism (MAXDOP) setting is equal to cipher or is greater than one, the number of workers may be much higher than the number of requests, and the limit may be reached much sooner than when MAXDOP is equal to ane.

Larn more about Sessions, workers, and requests.

Connect with the Defended Admin Connectedness (DAC) if needed

If a live incident is ongoing where the worker limit has been approached or reached, you may receive Error 10928 when y'all connect using SQL Server Management Studio (SSMS) or Azure Data Studio. One session can connect using the Diagnostic Connection for Database Administrators (DAC) fifty-fifty when the maximum worker threshold has been reached.

To found a connection with the DAC from SSMS:

From the menu, select File > New > Database Engine Query
From the connexion dialog box in the Server Name field, enter admin:<fully_qualified_server_name> (this will exist something like admin:servername.database.windows.internet).
Select Options >>
Select the Connection Backdrop tab
In the Connect to database: box, type the name of your database
Select Connect.

If you receive Fault 40613, Database '%.*ls' on server '%.*ls' is not currently bachelor. Please retry the connection later. If the problem persists, contact customer back up, and provide them the session tracing ID of '%.*ls', this may indicate that some other session is already connected to the DAC. Just 1 session may connect to the DAC for a single database or an elastic pool at a time.

If you encounter the error 'Failed to connect to server' after selecting Connect, the DAC session may still have been established successfully if you are using a version of SSMS prior to 18.9. Early versions of SSMS attempted to provide Intellisense for connections to the DAC. This failed, as the DAC supports only a single worker and Intellisense requires a divide worker.

Yous cannot utilize a DAC connectedness with Object Explorer.

Review your max_worker_percent usage

To find resource consumption statistics for your database for 14 days, query the sys.resource_stats arrangement itemize view. The max_worker_percent column shows the percentage of workers used relative to the worker limit for your database. Connect to the master database on your logical server to query sys.resource_stats.

              SELECT start_time, end_time, database_name, sku, avg_cpu_percent, max_worker_percent, max_session_percent  FROM sys.resource_stats;

You tin also query resource consumption statistics from the final hour from the sys.dm_db_resource_stats dynamic management view. Connect directly to your database to query sys.dm_db_resource_stats.

              SELECT end_time, avg_cpu_percent, max_worker_percent, max_session_percent FROM sys.dm_db_resource_stats;

Lower worker usage when possible

Blocking chains can crusade a sudden surge in the number of workers in a database. A big book of concurrent parallel queries may cause a high number of workers. Increasing your max caste of parallelism (MAXDOP) or setting MAXDOP to cypher tin increase the number of active workers.

Triage an incident with bereft workers by following these steps:

Investigate if blocking is occurring or if yous can place a large volume of concurrent workers. Run the following query to examine current requests and check for blocking when your database is returning Error 10928. You may need to connect with the Dedicated Admin Connection (DAC) to execute the query.
```
                  SELECT     r.session_id, r.request_id, r.blocking_session_id, r.start_time,      r.status, r.command, DB_NAME(r.database_id) Every bit database_name,     (SELECT COUNT(*)          FROM sys.dm_os_tasks AS t          WHERE t.session_id=r.session_id and t.request_id=r.request_id) As worker_count,     i.parameters, i.event_info As input_buffer,     r.last_wait_type, r.open_transaction_count, r.total_elapsed_time, r.cpu_time,     r.logical_reads, r.writes, s.login_time, due south.login_name, s.program_name, s.host_name FROM sys.dm_exec_requests as r Join sys.dm_exec_sessions as south on r.session_id=due south.session_id OUTER APPLY sys.dm_exec_input_buffer (r.session_id,r.request_id) As i WHERE southward.is_user_process=ane; Get                                  
```
1. Look for rows with a blocking_session_id to identify blocked sessions. Detect each blocking_session_id in the list to determine if that session is also blocked. This will eventually atomic number 82 yous to the head blocker. Melody the caput blocker query.
2. To place a large book of concurrent workers, review the number of requests overall and the worker_count column for each request. Worker_count is the number of workers at the time sampled and may modify over time as the asking is executed. Tune queries to reduce resource utilization if the cause of increased workers is concurrent queries that are running at their optimal caste of parallelism. For more than information, run into Query Tuning/Hinting.
Evaluate the maximum caste of parallelism (MAXDOP) setting for the database.

Increment worker limits

If the database consistently reaches its limit despite addressing blocking, optimizing queries, and validating your MAXDOP setting, consider adding more than resources to the database to increase the worker limit.

Observe resource limits for Azure SQL Database by service tier and compute size:

Resources limits for unmarried databases using the vCore purchasing model
Resource limits for elastic pools using the vCore purchasing model
Resource limits for single databases using the DTU purchasing model
Resources limits for elastic pools using the DTU purchasing model

Learn more about Azure SQL Database resource governance of workers.

Error 10929: Resources ID: 1

10929: Resource ID: one. The %southward minimum guarantee is %d, maximum limit is %d and the electric current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. Run into http://get.microsoft.com/fwlink/?LinkId=267637 for help. Otherwise, delight try again afterwards.

Error 40501: The service is currently decorated

40501: The service is currently busy. Retry the asking after 10 seconds. Incident ID: %ls. Code: %d.

This is an engine throttling error, an indication that resource limits are being exceeded.

For more information virtually resource limits, see Logical SQL server resource limits.

Error 40544: The database has reached its size quota

40544: The database has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions. Incident ID: <ID>. Code: <code>.

This fault occurs when the database has reached its size quota.

The post-obit steps can either help yous work around the problem or provide you with more options:

Cheque the current size of the database by using the dashboard in the Azure portal.

Annotation

To identify which tables are consuming the most space and are therefore potential candidates for cleanup, run the following SQL query:

                  SELECT o.proper name,  SUM(p.row_count) Equally 'Row Count',  SUM(p.reserved_page_count) * 8.0 / 1024 AS 'Table Size (MB)' FROM sys.objects o Join sys.dm_db_partition_stats p on p.object_id = o.object_id Grouping BY o.name Order Past [Tabular array Size (MB)] DESC; Get

If the electric current size does not exceed the maximum size supported for your edition, you lot can utilize ALTER DATABASE to increase the MAXSIZE setting.
If the database is already by the maximum supported size for your edition, try i or more of the following steps:
- Perform normal database cleanup activities. For example, clean up the unwanted data past using truncate/delete, or move data out by using SQL Server Integration Services (SSIS) or the bulk copy program (bcp) utility.
- Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
- For database scaling, run across Calibration unmarried database resources and Scale rubberband pool resources.

Error 40549: Session is terminated because y'all have a long-running transaction

40549: Session is terminated considering you lot have a long-running transaction. Endeavour shortening your transaction.

If you repeatedly run across this error, try to resolve the issue by following these steps:

Run the following query to see any open sessions that have a high value for the duration_ms cavalcade:

                  SELECT     r.start_time, DATEDIFF(ms,start_time, SYSDATETIME()) every bit duration_ms,  	r.session_id, r.request_id, r.blocking_session_id,       r.status, r.command, DB_NAME(r.database_id) AS database_name,     i.parameters, i.event_info AS input_buffer,     r.last_wait_type, r.open_transaction_count, r.total_elapsed_time, r.cpu_time,     r.logical_reads, r.writes, s.login_time, s.login_name, southward.program_name, s.host_name FROM sys.dm_exec_requests as r Join sys.dm_exec_sessions every bit southward on r.session_id=south.session_id OUTER Utilise sys.dm_exec_input_buffer (r.session_id,r.request_id) Every bit i WHERE s.is_user_process=1 ORDER Past start_time ASC; Go

Yous may choose to ignore rows where the input_buffer column shows a query reading from sys.fn_MSxe_read_event_stream: these requests are related to Extended Event sessions.

Review the blocking_session_id column to meet if blocking is contributing to long-running transactions.
Consider batching your queries. For information on batching, see How to use batching to improve SQL Database application performance.

Fault 40551: The session has been terminated because of excessive TEMPDB usage

40551: The session has been terminated because of excessive TEMPDB usage. Endeavour modifying your query to reduce the temporary table infinite usage.

To piece of work around this issue, follow these steps:

Change the queries to reduce temporary table space usage.
Drop temporary objects later they're no longer needed.
Truncate tables or remove unused tables.

Error 40552: The session has been terminated because of excessive transaction log space usage

40552: The session has been terminated because of excessive transaction log space usage. Attempt modifying fewer rows in a single transaction.

To resolve this issue, try the following methods:

The consequence tin can occur because of insert, update, or delete operations. Try to reduce the number of rows that are operated on immediately by implementing batching or splitting into multiple smaller transactions.
The issue can occur considering of index rebuild operations. To work around this issue, make sure the number of rows that are afflicted in the tabular array * (average size of field that'southward updated in bytes + fourscore) < 2 gigabytes (GB).

Annotation

For an alphabetize rebuild, the average size of the field that'due south updated should be substituted by the average index size.

Error 40553: The session has been terminated because of excessive retentiveness usage

40553: The session has been terminated because of excessive memory usage. Attempt modifying your query to procedure fewer rows.

To work around this consequence, effort to optimize the query.

For an in-depth troubleshooting procedure, encounter Is my query running fine in the cloud?.

For more than data on other out of memory errors and sample queries, see Troubleshoot out of memory errors with Azure SQL Database.

Table of resource governance fault messages

Error code	Severity	Clarification
10928	xx	Resources ID: %d. The %s limit for the database is %d and has been reached. See 'http://become.microsoft.com/fwlink/?LinkId=267637' for assistance.. The Resource ID indicates the resource that has reached the limit. When Resource ID = one, this indicates a worker limit has been reached. Learn more than in Error 10928: Resources ID : 1. The request limit for the database is %d and has been reached. When Resources ID = ii, this indicates the session limit has been reached. Larn more about resource limits: • Logical SQL server resource limits • DTU-based limits for single databases • DTU-based limits for elastic pools • vCore-based limits for single databases • vCore-based limits for elastic pools • Azure SQL Managed Instance resource limits.
10929	20	Resource ID: %d. The %south minimum guarantee is %d, maximum limit is %d, and the current usage for the database is %d. However, the server is currently too busy to support requests greater than %d for this database. The Resource ID indicates the resource that has reached the limit. For worker threads, the Resources ID = 1. For sessions, the Resources ID = 2. For more than information, come across: • Logical SQL server resource limits • DTU-based limits for single databases • DTU-based limits for elastic pools • vCore-based limits for single databases • vCore-based limits for elastic pools • Azure SQL Managed Instance resource limits. Otherwise, attempt again later.
40544	20	The database has reached its size quota. Sectionalization or delete data, drop indexes, or consult the documentation for possible resolutions. For database scaling, see Calibration unmarried database resources and Calibration elastic puddle resources.
40549	sixteen	Session is terminated because you have a long-running transaction. Try shortening your transaction. For information on batching, see How to utilize batching to improve SQL Database awarding performance.
40550	16	The session has been terminated because it has acquired as well many locks. Try reading or modifying fewer rows in a single transaction. For information on batching, encounter How to apply batching to improve SQL Database awarding performance.
40551	16	The session has been terminated because of excessive `TEMPDB` usage. Try modifying your query to reduce the temporary table space usage. If y'all are using temporary objects, conserve space in the `TEMPDB` database past dropping temporary objects after they are no longer needed by the session. For more than data on tempdb limits in SQL Database, see Tempdb database in SQL Database.
40552	xvi	The session has been terminated because of excessive transaction log infinite usage. Try modifying fewer rows in a single transaction. For information on batching, see How to use batching to ameliorate SQL Database application operation. If you perform bulk inserts using the `bcp.exe` utility or the `Organization.Information.SqlClient.SqlBulkCopy` class, attempt using the `-b batchsize` or `BatchSize` options to limit the number of rows copied to the server in each transaction. If you are rebuilding an index with the `Change Alphabetize` argument, effort using the `REBUILD WITH ONLINE = ON` selection. For information on transaction log sizes for the vCore purchasing model, encounter: • vCore-based limits for single databases • vCore-based limits for elastic pools • Azure SQL Managed Instance resource limits.
40553	sixteen	The session has been terminated because of excessive retention usage. Try modifying your query to process fewer rows. Reducing the number of `ORDER By` and `GROUP BY` operations in your Transact-SQL code reduces the retentivity requirements of your query. For database scaling, see Scale unmarried database resources and Calibration rubberband pool resources. For more information on out of retentiveness errors and sample queries, encounter Troubleshoot out of retentiveness errors with Azure SQL Database.

Elastic puddle errors

The following errors are related to creating and using rubberband pools:

Fault code	Severity	Clarification	Cosmetic activity
1132	17	The rubberband pool has reached its storage limit. The storage usage for the elastic pool cannot exceed (%d) MBs. Attempting to write data to a database when the storage limit of the elastic pool has been reached. For information on resource limits, meet: • DTU-based limits for elastic pools • vCore-based limits for elastic pools.	Consider increasing the DTUs of and/or adding storage to the rubberband pool if possible in guild to increase its storage limit, reduce the storage used by private databases within the elastic pool, or remove databases from the elastic pool. For elastic pool scaling, see Scale rubberband pool resources. For more than data on removing unused space from databases, come across Manage file space for databases in Azure SQL Database.
10929	16	The %s minimum guarantee is %d, maximum limit is %d, and the current usage for the database is %d. Even so, the server is currently besides busy to support requests greater than %d for this database. For data on resource limits, see: • DTU-based limits for elastic pools • vCore-based limits for elastic pools. Otherwise, endeavour again later. DTU / vCore min per database; DTU / vCore max per database. The full number of concurrent workers across all databases in the rubberband puddle attempted to exceed the puddle limit.	Consider increasing the DTUs or vCores of the elastic pool if possible in guild to increase its worker limit, or remove databases from the elastic pool.
40844	16	Database '%ls' on Server '%ls' is a '%ls' edition database in an elastic pool and cannot have a continuous copy human relationship.	North/A
40857	16	Elastic puddle not found for server: '%ls', elastic pool name: '%ls'. Specified elastic puddle does not be in the specified server.	Provide a valid rubberband pool name.
40858	16	Elastic pool '%ls' already exists in server: '%ls'. Specified elastic pool already exists in the specified server.	Provide new elastic pool proper name.
40859	16	Elastic pool does not back up service tier '%ls'. 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.
40860	16	Rubberband pool '%ls' and service objective '%ls' combination is invalid. Elastic puddle and service tier can be specified together only if resource type is specified as 'ElasticPool'.	Specify correct combination of elastic pool and service tier.
40861	sixteen	The database edition '%.ls' cannot be different than the elastic pool service tier which is '%.ls'. The database edition is different than the elastic pool service tier.	Practise not specify a database edition that is dissimilar than the elastic pool service tier. Note that the database edition does non need to be specified.
40862	16	Elastic pool proper noun must be specified if the elastic pool service objective is specified. Elastic puddle service objective does not uniquely identify an elastic pool.	Specify the elastic pool name if using the rubberband puddle service objective.
40864	16	The DTUs for the elastic pool must be at to the lowest degree (%d) DTUs for service tier '%.*ls'. Attempting to set the DTUs for the elastic puddle below the minimum limit.	Retry setting the DTUs for the elastic pool to at to the lowest degree the minimum limit.
40865	16	The DTUs for the elastic pool cannot exceed (%d) DTUs for service tier '%.*ls'. Attempting to set the DTUs for the elastic pool in a higher place the maximum limit.	Retry setting the DTUs for the elastic pool to no greater than the maximum limit.
40867	16	The DTU max per database must exist at least (%d) for service tier '%.*ls'. Attempting to set the DTU max per database below the supported limit.	Consider using the elastic pool service tier that supports the desired setting.
40868	16	The DTU max per database cannot exceed (%d) for service tier '%.*ls'. Attempting to set the DTU max per database across the supported limit.	Consider using the rubberband pool service tier that supports the desired setting.
40870	xvi	The DTU min per database cannot exceed (%d) for service tier '%.*ls'. Attempting to set the DTU min per database across the supported limit.	Consider using the elastic pool service tier that supports the desired setting.
40873	16	The number of databases (%d) and DTU min per database (%d) cannot exceed the DTUs of the elastic puddle (%d). Attempting to specify DTU min for databases in the rubberband puddle that exceeds the DTUs of the elastic puddle.	Consider increasing the DTUs of the elastic pool, or decrease the DTU min per database, or decrease the number of databases in the rubberband pool.
40877	16	An rubberband pool cannot be deleted unless information technology does not contain any databases. The elastic puddle contains one or more databases and therefore cannot exist deleted.	Remove databases from the elastic pool in order to delete information technology.
40881	16	The rubberband puddle '%.*ls' has reached its database count limit. The database count limit for the rubberband pool cannot exceed (%d) for an elastic pool with (%d) DTUs. Attempting to create or add database to elastic pool when the database count limit of the rubberband pool has been reached.	Consider increasing the DTUs of the rubberband pool if possible in order to increase its database limit, or remove databases from the elastic pool.
40889	16	The DTUs or storage limit for the elastic pool '%.*ls' cannot be decreased since that would non provide sufficient storage space for its databases. Attempting to decrease the storage limit of the elastic puddle below its storage usage.	Consider reducing the storage usage of individual databases in the rubberband puddle or remove databases from the pool in order to reduce its DTUs or storage limit.
40891	16	The DTU min per database (%d) cannot exceed the DTU max per database (%d). Attempting to gear up the DTU min per database college than the DTU max per database.	Ensure the DTU min per databases does non exceed the DTU max per database.
TBD	xvi	The storage size for an individual database in an elastic pool cannot exceed the max size immune by '%.*ls' service tier elastic pool. The max size for the database exceeds the max size allowed past the elastic pool service tier.	Set the max size of the database inside the limits of the max size immune by the elastic pool service tier.

This issue occurs because the account doesn't accept permission to access the principal database. Only past default, SQL Server Management Studio (SSMS) tries to connect to the master database.

To resolve this upshot, follow these steps:

On the login screen of SSMS, select Options, and then select Connection Properties.
In the Connect to database field, enter the user'southward default database proper noun as the default login database, and so select Connect.

Read-merely errors

If you attempt to write to a database that is read-only, yous'll receive an error. In some scenarios, the crusade of the database's read-merely status may not be immediately clear.

Error 3906: Failed to update database "DatabaseName" because the database is read-only.

When attempting to change a read-just database, the following mistake will be raised.

              Msg 3906, Level 16, State 2, Line i Failed to update database "%d" because the database is read-merely.

You may be continued to a read-only replica

For both Azure SQL Database and Azure SQL Managed Instance, y'all may exist continued to a database on a read-only replica. In this example, the following query using the DATABASEPROPERTYEX() office will return READ_ONLY:

              SELECT DATABASEPROPERTYEX(DB_NAME(), 'Updateability'); GO

If you're connecting using SQL Server Direction Studio, verify if you have specified ApplicationIntent=ReadOnly in the Additional Connection Parameters tab on your connection options.

If the connection is from an application or a client using a connection string, validate if the connexion cord has specified ApplicationIntent=ReadOnly. Learn more in Connect to a read-just replica.

The database may be ready to read-only

If you're using Azure SQL Database, the database itself may have been set to read-only. Y'all can verify the database's status with the post-obit query:

              SELECT name, is_read_only FROM sys.databases WHERE database_id = DB_ID();

You lot tin can modify the read-only condition for a database in Azure SQL Database using ALTER DATABASE Transact-SQL. You can't currently set a database in a managed instance to read-only.

Ostend whether an fault is caused by a connectivity issue

To confirm whether an error is caused by a connectivity issue, review the stack trace for frames that show calls to open a connection like the following ones (annotation the reference to the SqlConnection class):

              System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)  at Organisation.Data.SqlClient.SqlConnection.Open()  at AzureConnectionTest.Program.Chief(String[] args) ClientConnectionId:<Customer connectedness ID>

When the exception is triggered past query issues, you lot'll notice a call stack that's similar to the following (annotation the reference to the SqlCommand class). In this situation, tune your queries.

                              at Organization.Information.SqlClient.SqlCommand.ExecuteReader()   at AzureConnectionTest.Program.Main(String[] args)   ClientConnectionId:<Client ID>

For additional guidance on fine-tuning performance, encounter the following resource:

How to maintain Azure SQL indexes and statistics
Transmission tune query operation in Azure SQL Database
Monitoring performance Azure SQL Database by using dynamic management views
Operating the Query Store in Azure SQL Database

Steps to gear up common connection problems

Make sure that TCP/IP is enabled as a client protocol on the application server. For more information, see Configure client protocols. On application servers where yous don't have SQL tools installed, verify that TCP/IP is enabled by running cliconfg.exe (SQL Server Client Network utility).
Check the application's connection string to make sure it'due south configured correctly. For example, make sure that the connection string specifies the correct port (1433) and fully qualified server name. Meet Get connection information.
Effort increasing the connectedness timeout value. Nosotros recommend using a connectedness timeout of at least thirty seconds.
Exam the connectivity betwixt the application server and the Azure SQL Database by using SQL Server Direction Studio (SSMS), a UDL file, ping, or telnet. For more data, see Troubleshooting connectivity issues and Diagnostics for connectivity issues.

Note

Equally a troubleshooting step, you can also examination connectivity on a different client computer.
As a best practice, make sure that the retry logic is in place. For more than data about retry logic, encounter Troubleshoot transient faults and connection errors to SQL Database.

If these steps don't resolve your problem, attempt to collect more data and so contact support. If your application is a cloud service, enable logging. This step returns a UTC fourth dimension stamp of the failure. Additionally, SQL Database returns the tracing ID. Microsoft Customer Support Services can use this information.

For more information about how to enable logging, see Enable diagnostics logging for apps in Azure App Service.

Side by side steps

Acquire more than nearly related topics in the post-obit articles:

Azure SQL Database connectivity architecture
Azure SQL Database and Azure Synapse Analytics network access controls
Troubleshooting transaction log errors with Azure SQL Database and Azure SQL Managed Instance
Troubleshoot transient connection errors in SQL Database and SQL Managed Instance
Analyze and prevent deadlocks in Azure SQL Database

Feedback

Submit and view feedback for

hallherivink.blogspot.com

Source: https://docs.microsoft.com/en-us/azure/azure-sql/database/troubleshoot-common-errors-issues