Skip to content

Commit e048f3b

Browse files
1 parent a8a9271 commit e048f3b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sql-database/sql-database-managed-instance.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -297,7 +297,7 @@ The following diagram outlines surface area compatibility in managed instance:
297297

298298
### Key differences between SQL Server on-premises and in a managed instance
299299

300-
The managed instance deployment option benefits from being always-up-to-date in the cloud, which means that some features in on-premises SQL Server may be either obsolete, retired, or have alternatives. There are specific cases when tools need to recognize that a particular feature works in a slightly different way or that service is not running in an environment you do not fully control:
300+
The managed instance deployment option benefits from being always-up-to-date in the cloud, which means that some features in on-premises SQL Server may be either obsolete, retired, or have alternatives. There are specific cases when tools need to recognize that a particular feature works in a slightly different way or that the service is running in an environment you do not fully control:
301301

302302
- High-availability is built in and pre-configured using technology similar to [Always On Availability Groups](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/always-on-availability-groups-sql-server).
303303
- Automated backups and point in time restore. Customer can initiate `copy-only` backups that do not interfere with automatic backup chain.

0 commit comments

Comments
 (0)