Skip to content

Commit d3933e0

Browse files
Update user-initiated-failover.md (#33620)
1 parent 213bdbf commit d3933e0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-sql/managed-instance/user-initiated-failover.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ It's possible to fail over a primary node in the General Purpose (GP) and Busine
3030

3131
The entire failover operation consists of bringing the SQL Server database engine process online, validating the database state, and then finally redirecting the client connections to the new SQL process. Client connections only fail for a short period of time, typically under a minute, during the final step of the failover operation.
3232

33-
You might execute a manual failover to restart the engine process on a different node for the following reasons:
33+
You might execute a manual failover to restart the engine process for the following reasons:
3434

3535
- Failed logins, or slowness due to performance issues.
3636
- Testing application for failover resiliency before deploying to production.

0 commit comments

Comments
 (0)