Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit ae062ec

Browse files
committed
Feedback from comments
1 parent 358ccc3 commit ae062ec

1 file changed

Lines changed: 40 additions & 40 deletions

File tree

docs/sql-server/end-of-support/sql-server-end-of-life-overview.md

Lines changed: 40 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Each version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] is bac
2929

3030
Once your [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] has reached the end of support stage, you can choose to:
3131

32-
- Migrate your workload to [Azure SQL](/azure/sql-database/sql-database-paas-vs-sql-server-iaas).
32+
- [Migrate](/azure/azure-sql/migration-guides/) your workload to [Azure SQL](/azure/sql-database/sql-database-paas-vs-sql-server-iaas).
3333
- Migrate your workload to an Azure Virtual Machine as-is for [free Extended Security Updates](/azure/virtual-machines/windows/sql/virtual-machines-windows-sql-server-2008-eos-extend-support).
3434
- Upgrade to a current version of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
3535
- Purchase an [Extended Security Updates subscription](https://www.microsoft.com/cloud-platform/extended-security-updates).
@@ -93,6 +93,45 @@ The following image provides an example of innovation over the various versions
9393

9494
:::image type="content" source="media/sql-server-end-of-life-overview/sql-server-version-improvements.png" alt-text="25 years of SQL Server innovation":::
9595

96+
## Azure SQL Managed Instance
97+
98+
If you'd like to take advantage of offloading maintenance and cost, but find the feature set of an [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] single database too limiting, you can move to [SQL Managed Instance](/azure/sql-database/sql-database-managed-instance). A managed instance closely resembles an on-premises [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], without having to worry about such things as hardware failure, or patching. Managed Instance is a collection of system and user databases with a shared set of resources that is lift-and-shift ready, and can be used for most migrations to the cloud. This option is best for new applications or existing on-premises applications that want to use the latest stable [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] features and that are migrated to the cloud with minimal changes.
99+
100+
### Benefits
101+
102+
- **Cost**: You can save costs by offloading software and hardware maintenance.
103+
- **Lift and shift**: You can lift and shift your entire [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on-premises instance to a managed instance, including all databases with minimal to no database change.
104+
- **Features**: Closely matches the features of an on-premises instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], such as cross-database queries, transactional replication publishing and distribution, SQL job scheduling, and CLR support.
105+
- **Scalability**: Within a managed instance, all databases share resources, and it's possible to scale up and down at any time without downtime.
106+
- **Automation**: Patching and backups happening automatically, saving you valuable maintenance time.
107+
- **Availability**: The cost of the service includes both storage and high availability, with 99.99% availability guaranteed.
108+
- **Intelligent Insights**: Gain insight about the performance of your databases with built-in intelligence analytics.
109+
- **Versionless**: [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] is versionless, meaning you're always on the latest version, and never have to worry about upgrading, or downtime. Plus, you're always on the latest and greatest, with our latest stable features being released to the cloud first.
110+
- **Low risk for database applications**: When the database compatibility is at the same level as the on-premises databases, existing database applications are protected from functional and performance changes that can have detrimental effects. An application only needs to be fully re-certified when it needs to use features available in a newer database compatibility setting. For more information, see [Compatibility Certification](../../database-engine/install-windows/compatibility-certification.md).
111+
112+
### Considerations
113+
114+
- **Cost**: The managed instance option can be more costly than the single database option.
115+
- **Transact-SQL differences**: There are some [!INCLUDE[tsql](../../includes/tsql-md.md)] (T-SQL) differences between a single database and an on-premises [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
116+
- **Deployment**: Deploying a managed instance can take more time than a single database.
117+
- **Feature limitation**: Although a managed instance shares most features with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there are still some features that are unsupported.
118+
- **Size limitation**: The combined storage size for all databases within a managed instance are limited to 8 TB, as opposed to 524 PB for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on-premises.
119+
- **Networking**: The networking requirements for a managed instance add an extra layer of complexity to your infrastructure, and requires either an Azure ExpressRoute or VPN Gateway.
120+
- **Maintenance time**: You have no guarantee for the exact maintenance time, though it's nearly transparent.
121+
122+
### Resources
123+
124+
- [SQL Managed Instance overview](/azure/sql-database/sql-database-managed-instance)
125+
- [Choosing an Azure SQL option](/azure/sql-database/sql-database-paas-vs-sql-server-iaas)
126+
- [SQL Database feature comparison](/azure/sql-database/sql-database-features)
127+
- [Migrate SQL Server to Azure SQL Managed Instance](/azure/sql-database/sql-database-managed-instance-migrate)
128+
- [Broader migration process](/azure/cloud-adoption-framework/migrate/expanded-scope/sql-migration)
129+
130+
Tools:
131+
132+
- [Data Migration Assistant](../../dma/dma-overview.md)
133+
- [Database Migration Service](/azure/dms/dms-overview)
134+
96135
## Extend support
97136

98137
If you're not ready to upgrade, and you're not ready to move to the cloud, you have the ability to purchase an Extended Security Updates subscription to receive **Critical** security updates for up to three years past the end of the support date.
@@ -198,45 +237,6 @@ Tools:
198237
- [Data Migration Assistant](../../dma/dma-overview.md)
199238
- [Database Migration Service](/azure/dms/dms-overview)
200239

201-
## Azure SQL Managed Instance
202-
203-
If you'd like to take advantage of offloading maintenance and cost, but find the feature set of an [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] single database too limiting, you can move to [SQL Managed Instance](/azure/sql-database/sql-database-managed-instance). A managed instance closely resembles an on-premises [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], without having to worry about such things as hardware failure, or patching. Managed Instance is a collection of system and user databases with a shared set of resources that is lift-and-shift ready, and can be used for most migrations to the cloud. This option is best for new applications or existing on-premises applications that want to use the latest stable [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)] features and that are migrated to the cloud with minimal changes.
204-
205-
### Benefits
206-
207-
- **Cost**: You can save costs by offloading software and hardware maintenance.
208-
- **Lift and shift**: You can lift and shift your entire [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on-premises instance to a managed instance, including all databases with minimal to no database change.
209-
- **Features**: Closely matches the features of an on-premises instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], such as cross-database queries, transactional replication publishing and distribution, SQL job scheduling, and CLR support.
210-
- **Scalability**: Within a managed instance, all databases share resources, and it's possible to scale up and down at any time without downtime.
211-
- **Automation**: Patching and backups happening automatically, saving you valuable maintenance time.
212-
- **Availability**: The cost of the service includes both storage and high availability, with 99.99% availability guaranteed.
213-
- **Intelligent Insights**: Gain insight about the performance of your databases with built-in intelligence analytics.
214-
- **Versionless**: [!INCLUDE[ssSDSfull](../../includes/sssdsfull-md.md)] is versionless, meaning you're always on the latest version, and never have to worry about upgrading, or downtime. Plus, you're always on the latest and greatest, with our latest stable features being released to the cloud first.
215-
- **Low risk for database applications**: When the database compatibility is at the same level as the on-premises databases, existing database applications are protected from functional and performance changes that can have detrimental effects. An application only needs to be fully re-certified when it needs to use features available in a newer database compatibility setting. For more information, see [Compatibility Certification](../../database-engine/install-windows/compatibility-certification.md).
216-
217-
### Considerations
218-
219-
- **Cost**: The managed instance option can be more costly than the single database option.
220-
- **Transact-SQL differences**: There are some [!INCLUDE[tsql](../../includes/tsql-md.md)] (T-SQL) differences between a single database and an on-premises [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].
221-
- **Deployment**: Deploying a managed instance can take more time than a single database.
222-
- **Feature limitation**: Although a managed instance shares most features with [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], there are still some features that are unsupported.
223-
- **Size limitation**: The combined storage size for all databases within a managed instance are limited to 8 TB, as opposed to 524 PB for [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] on-premises.
224-
- **Networking**: The networking requirements for a managed instance add an extra layer of complexity to your infrastructure, and requires either an Azure ExpressRoute or VPN Gateway.
225-
- **Maintenance time**: You have no guarantee for the exact maintenance time, though it's nearly transparent.
226-
227-
### Resources
228-
229-
- [SQL Managed Instance overview](/azure/sql-database/sql-database-managed-instance)
230-
- [Choosing an Azure SQL option](/azure/sql-database/sql-database-paas-vs-sql-server-iaas)
231-
- [SQL Database feature comparison](/azure/sql-database/sql-database-features)
232-
- [Migrate SQL Server to Azure SQL Managed Instance](/azure/sql-database/sql-database-managed-instance-migrate)
233-
- [Broader migration process](/azure/cloud-adoption-framework/migrate/expanded-scope/sql-migration)
234-
235-
Tools:
236-
237-
- [Data Migration Assistant](../../dma/dma-overview.md)
238-
- [Database Migration Service](/azure/dms/dms-overview)
239-
240240
## Non-SQL options
241241

242242
For certain types of applications, you may also consider a non-relational or NoSQL solution, such as Azure Cosmos DB or Azure table storage.

0 commit comments

Comments
 (0)