The following table lists various transient errors that applications can receive when connecting to Azure SQL Database. However, these events can occasionally take longer to finish, such as when a large transaction causes a long-running recovery. Most reconfiguration events are generally short-lived and should be completed in less than 60 seconds at most. Database reconfiguration events occur because of a planned event (for example, a software upgrade) or an unplanned event (for example, a process crash, or load balancing). This kind of error condition is called a transient fault. This dynamic behavior might cause your client program to lose its connection to the database or instance.
The Azure infrastructure has the ability to dynamically reconfigure servers when heavy workloads arise in the SQL Database service. Transient fault error messages (40197, 40613 and others) Additionally, if the maximum limit on some Azure SQL Database or SQL Managed Instance resources is reached, you can no longer connect. These connection problems can be caused by reconfiguration, firewall settings, a connection timeout, incorrect login information, or failure to apply best practices and design guidelines during the application design process. You receive error messages when the connection to Azure SQL Database or Azure SQL Managed Instance fails.
0 kommentar(er)
