You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// Cannot process request. Too many operations in progress for subscription "%ld".
47
-
// The service is busy processing multiple requests for this subscription.
48
-
// Requests are currently blocked for resource optimization. Query sys.dm_operation_status for operation status.
49
-
// Wait until pending requests are complete or delete one of your pending requests and retry your request later.
50
-
case49920:
51
-
// SQL Error Code: 49919
52
-
// Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
53
-
// The service is busy processing multiple create or update requests for your subscription or server.
54
-
// Requests are currently blocked for resource optimization. Query sys.dm_operation_status for pending operations.
55
-
// Wait till pending create or update requests are complete or delete one of your pending requests and
56
-
// retry your request later.
57
-
case49919:
58
-
// SQL Error Code: 49918
59
-
// Cannot process request. Not enough resources to process request.
60
-
// The service is currently busy.Please retry the request later.
61
-
case49918:
62
-
// SQL Error Code: 41839
63
-
// Transaction exceeded the maximum number of commit dependencies.
64
-
case41839:
65
-
// SQL Error Code: 41325
66
-
// The current transaction failed to commit due to a serializable validation failure.
67
-
case41325:
68
-
// SQL Error Code: 41305
69
-
// The current transaction failed to commit due to a repeatable read validation failure.
70
-
case41305:
71
-
// SQL Error Code: 41302
72
-
// The current transaction attempted to update a record that has been updated since the transaction started.
73
-
case41302:
74
-
// SQL Error Code: 41301
75
-
// Dependency failure: a dependency was taken on another transaction that later failed to commit.
76
-
case41301:
77
-
// SQL Error Code: 40613
78
-
// Database XXXX on server YYYY is not currently available. Please retry the connection later.
79
-
// If the problem persists, contact customer support, and provide them the session tracing ID of ZZZZZ.
80
-
case40613:
81
-
// SQL Error Code: 40501
82
-
// The service is currently busy. Retry the request after 10 seconds. Code: (reason code to be decoded).
83
-
case40501:
84
-
// SQL Error Code: 40197
85
-
// The service has encountered an error processing your request. Please try again.
86
-
case40197:
87
-
// SQL Error Code: 10929
88
-
// Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d.
89
-
// However, the server is currently too busy to support requests greater than %d for this database.
90
-
// For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again.
91
-
case10929:
92
-
// SQL Error Code: 10928
93
-
// Resource ID: %d. The %s limit for the database is %d and has been reached. For more information,
94
-
// see http://go.microsoft.com/fwlink/?LinkId=267637.
95
-
case10928:
96
-
// SQL Error Code: 10060
97
-
// A network-related or instance-specific error occurred while establishing a connection to SQL Server.
98
-
// The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server
99
-
// is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed
100
-
// because the connected party did not properly respond after a period of time, or established connection failed
101
-
// because connected host has failed to respond.)"}
102
-
case10060:
103
-
// SQL Error Code: 10054
104
-
// A transport-level error has occurred when sending the request to the server.
105
-
// (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
106
-
case10054:
107
-
// SQL Error Code: 10053
108
-
// A transport-level error has occurred when receiving results from the server.
109
-
// An established connection was aborted by the software in your host machine.
110
-
case10053:
111
-
// SQL Error Code: 1205
112
-
// Deadlock
113
-
case1205:
114
-
// SQL Error Code: 233
115
-
// The client was unable to establish a connection because of an error during connection initialization process before login.
116
-
// Possible causes include the following: the client tried to connect to an unsupported version of SQL Server;
117
-
// the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum
118
-
// allowed connections) on the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by
119
-
// the remote host.)
120
-
case233:
121
-
// SQL Error Code: 121
122
-
// The semaphore timeout period has expired
123
-
case121:
124
-
// SQL Error Code: 64
125
-
// A connection was successfully established with the server, but then an error occurred during the login process.
126
-
// (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
127
-
case64:
128
-
// DBNETLIB Error Code: 20
129
-
// The instance of SQL Server you attempted to connect to does not support encryption.
130
-
case20:
131
-
returntrue;
132
-
// This exception can be thrown even if the operation completed successfully, so it's safer to let the application fail.
133
-
// DBNETLIB Error Code: -2
134
-
// Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.
135
-
//case -2:
136
-
}
137
-
}
17
+
privatestaticreadonlyUInt128Ten=10;
138
18
139
-
returnfalse;
19
+
/// <summary>
20
+
/// This API supports the Entity Framework Core infrastructure and is not intended to be used
21
+
/// directly from your code. This API may change or be removed in future releases.
// Cannot process request. Too many operations in progress for subscription "%ld".
35
+
// The service is busy processing multiple requests for this subscription.
36
+
// Requests are currently blocked for resource optimization. Query sys.dm_operation_status for operation status.
37
+
// Wait until pending requests are complete or delete one of your pending requests and retry your request later.
38
+
case49920:
39
+
// SQL Error Code: 49919
40
+
// Cannot process create or update request. Too many create or update operations in progress for subscription "%ld".
41
+
// The service is busy processing multiple create or update requests for your subscription or server.
42
+
// Requests are currently blocked for resource optimization. Query sys.dm_operation_status for pending operations.
43
+
// Wait till pending create or update requests are complete or delete one of your pending requests and
44
+
// retry your request later.
45
+
case49919:
46
+
// SQL Error Code: 49918
47
+
// Cannot process request. Not enough resources to process request.
48
+
// The service is currently busy.Please retry the request later.
49
+
case49918:
50
+
// SQL Error Code: 41839
51
+
// Transaction exceeded the maximum number of commit dependencies.
52
+
case41839:
53
+
// SQL Error Code: 41325
54
+
// The current transaction failed to commit due to a serializable validation failure.
55
+
case41325:
56
+
// SQL Error Code: 41305
57
+
// The current transaction failed to commit due to a repeatable read validation failure.
58
+
case41305:
59
+
// SQL Error Code: 41302
60
+
// The current transaction attempted to update a record that has been updated since the transaction started.
61
+
case41302:
62
+
// SQL Error Code: 41301
63
+
// Dependency failure: a dependency was taken on another transaction that later failed to commit.
64
+
case41301:
65
+
// SQL Error Code: 40613
66
+
// Database XXXX on server YYYY is not currently available. Please retry the connection later.
67
+
// If the problem persists, contact customer support, and provide them the session tracing ID of ZZZZZ.
68
+
case40613:
69
+
// SQL Error Code: 40501
70
+
// The service is currently busy. Retry the request after 10 seconds. Code: (reason code to be decoded).
71
+
case40501:
72
+
// SQL Error Code: 40197
73
+
// The service has encountered an error processing your request. Please try again.
74
+
case40197:
75
+
// SQL Error Code: 10929
76
+
// Resource ID: %d. The %s minimum guarantee is %d, maximum limit is %d and the current usage for the database is %d.
77
+
// However, the server is currently too busy to support requests greater than %d for this database.
78
+
// For more information, see http://go.microsoft.com/fwlink/?LinkId=267637. Otherwise, please try again.
79
+
case10929:
80
+
// SQL Error Code: 10928
81
+
// Resource ID: %d. The %s limit for the database is %d and has been reached. For more information,
82
+
// see http://go.microsoft.com/fwlink/?LinkId=267637.
83
+
case10928:
84
+
// SQL Error Code: 10060
85
+
// A network-related or instance-specific error occurred while establishing a connection to SQL Server.
86
+
// The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server
87
+
// is configured to allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed
88
+
// because the connected party did not properly respond after a period of time, or established connection failed
89
+
// because connected host has failed to respond.)"}
90
+
case10060:
91
+
// SQL Error Code: 10054
92
+
// A transport-level error has occurred when sending the request to the server.
93
+
// (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
94
+
case10054:
95
+
// SQL Error Code: 10053
96
+
// A transport-level error has occurred when receiving results from the server.
97
+
// An established connection was aborted by the software in your host machine.
98
+
case10053:
99
+
// SQL Error Code: 1205
100
+
// Deadlock
101
+
case1205:
102
+
// SQL Error Code: 233
103
+
// The client was unable to establish a connection because of an error during connection initialization process before login.
104
+
// Possible causes include the following: the client tried to connect to an unsupported version of SQL Server;
105
+
// the server was too busy to accept new connections; or there was a resource limitation (insufficient memory or maximum
106
+
// allowed connections) on the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by
107
+
// the remote host.)
108
+
case233:
109
+
// SQL Error Code: 121
110
+
// The semaphore timeout period has expired
111
+
case121:
112
+
// SQL Error Code: 64
113
+
// A connection was successfully established with the server, but then an error occurred during the login process.
114
+
// (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
115
+
case64:
116
+
// DBNETLIB Error Code: 20
117
+
// The instance of SQL Server you attempted to connect to does not support encryption.
118
+
case20:
119
+
returntrue;
120
+
// This exception can be thrown even if the operation completed successfully, so it's safer to let the application fail.
121
+
// DBNETLIB Error Code: -2
122
+
// Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.
0 commit comments