Skip to content

Commit a47e6bc

Browse files
committed
formatting
1 parent 602a486 commit a47e6bc

4 files changed

Lines changed: 23 additions & 24 deletions

File tree

12.1 KB
Loading

docs/sql-server/end-of-support/sql-server-extended-security-updates.md

Lines changed: 18 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: "Extended security updates overview"
3-
description: Learn how to get extended security updates for your end-of-support and end-of-life SQL Server products, such as SQL Server 2008, and SQL Server 2008 R2.
3+
description: Learn how to use the SQL Server registry to get extended security updates for your end-of-support and end-of-life SQL Server products, such as SQL Server 2008, and SQL Server 2008 R2.
44
ms.custom: ""
55
ms.date: "12/09/2019"
66
ms.prod: sql
@@ -16,30 +16,30 @@ monikerRange: ">=sql-server-2016||=sqlallproducts-allversions"
1616

1717
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md-winonly](../../includes/appliesto-ss-xxxx-xxxx-xxx-md-winonly.md)]
1818

19-
Once SQL Server has reached the end of its support life cycle, you have the option to purchase an Extended Security Update subscription for your servers and remain protected for up to three years, until you are ready to upgrade to a newer version of SQL Server.
19+
Once SQL Server has reached the end of its support life cycle, you have the option to purchase an Extended Security Update (ESU) subscription for your servers and remain protected for up to three years, until you are ready to upgrade to a newer version of SQL Server. You can then use the **SQL Server registry** service in the Azure portal to register your end-of-support SQL Server instance and download updates when they are made available.
2020

21-
This article provides details about extended security updates for SQL Server 2008 and SQL Server 2008 R2. For more information about other options, see [End of support options](sql-server-end-of-life-overview.md).
21+
This article provides information for using the SQL Server registry service to receive Extended Security Updates for SQL Server 2008 and SQL Server 2008 R2. For more information about other options, see [End of support options](sql-server-end-of-life-overview.md).
2222

23-
Microsoft recommends applying ESU patches as soon as they are available to keep your SQL Server instance protected. For detailed information and clarification, see the [ESU FAQ page](https://www.microsoft.com/en-us/cloud-platform/extended-security-updates).
23+
Microsoft recommends applying ESU patches as soon as they are available to keep your SQL Server instance protected. For detailed information about ESUs, see the [ESU FAQ page](https://www.microsoft.com/cloud-platform/extended-security-updates).
2424

2525
[Extended support for SQL Server 2008 and SQL Server 2008 R2 ended on July 10, 2019](https://www.microsoft.com/cloud-platform/windows-sql-server-2008).
2626

27-
## What are Extended Security updates
28-
Extended Security Updates (ESUs) for SQL Server and SQL Server 2008 R2 include provision of security updates for customers who have purchased an Extended Support Update subscription.
27+
## What are Extended Security Updates
28+
Extended Security Updates (ESUs) for SQL Server 2008 and SQL Server 2008 R2 include provision of security updates for customers who have purchased an Extended Support Update subscription.
2929

30-
ESUs are distributed **if and when available**, when a security vulnerability is discovered and is rated as **Critical** by [Microsoft Security Response Center (MSRC)](https://portal.msrc.microsoft.com). Therefore, there is no regular release cadence for SQL Server ESUs.
30+
ESUs are distributed **if and when available**, once a security vulnerability is discovered and is rated as **Critical** by [Microsoft Security Response Center (MSRC)](https://portal.msrc.microsoft.com). Therefore, there is no regular release cadence for SQL Server ESUs.
3131

3232
ESUs do not include:
3333
- New features
3434
- Customer-requested non-security hotfixes
35-
- Design change requests.
35+
- Design change requests
3636

3737
### Support
3838

39-
ESUs do not include technical support, but you can use an active support contract such as [Software Assurance](https://www.microsoft.com/en-us/licensing/licensing-programs/software-assurance-default?activetab=software-assurance-default-pivot%3aprimaryr3) or Premier/Unified Support on SQL Server 2008 / 2008 R2 to get technical support on workloads covered by ESUs if you choose to stay on-premises. Alternatively, if you're hosting on Azure, you can use an Azure Support plan to get technical support.
39+
ESUs do not include technical support, but you can use an active support contract such as [Software Assurance](https://www.microsoft.com/licensing/licensing-programs/software-assurance-default?activetab=software-assurance-default-pivot%3aprimaryr3) or Premier/Unified Support on SQL Server 2008 / 2008 R2 to get technical support on workloads covered by ESUs if you choose to stay on-premises. Alternatively, if you're hosting on Azure, you can use an Azure Support plan to get technical support.
4040

4141
> [!NOTE]
42-
> Microsoft cannot provide technical support for SQL Server 2008 / 2008 R2 instances (both on-premises, and in hosting environments) that are not covered with an ESU subscription.
42+
> Microsoft cannot provide technical support for SQL Server 2008 and 2008 R2 instances (both on-premises, and in hosting environments) that are not covered with an ESU subscription.
4343
4444

4545
## ESU Availability
@@ -48,9 +48,9 @@ ESUs are available to customers running their workload in Azure, on-premises, or
4848

4949
**In Azure**: If you migrate your workloads to Azure Virtual Machines (IaaS), you will have access to Extended Security Updates for SQL Server 2008 and 2008 R2 for three years after the End of Support for **no additional charges** above the cost of running the virtual machine. Customers do not need Software Assurance to receive Extended Security Updates in Azure.
5050

51-
**On-premises or hosted environments**: If you have Software Assurance, you can purchase Extended Security Updates for three years after the End of Support date, under an Enterprise Agreement (EA), Enterprise Subscription Agreement (EAS), a Server & Cloud Enrollment (SCE), or an Enrollment for Education Solutions **EES**. You can purchase Extended Security Updates only for the servers you need to cover. Extended Security Updates can be purchased directly from Microsoft or a Microsoft licensing partner.
51+
**On-premises or hosted environments**: If you have Software Assurance, you can purchase Extended Security Updates for three years after the End of Support date, under an Enterprise Agreement (EA), Enterprise Subscription Agreement (EAS), a Server & Cloud Enrollment (SCE), or an Enrollment for Education Solutions (EES). You can purchase Extended Security Updates only for the servers you need to cover. Extended Security Updates can be purchased directly from Microsoft or a Microsoft licensing partner.
5252

53-
For more information, see the [Extended Security Updates frequently asked questions](https://www.microsoft.com/en-us/cloud-platform/extended-security-updates).
53+
For more information, see the [Extended Security Updates frequently asked questions](https://www.microsoft.com/cloud-platform/extended-security-updates).
5454

5555
## ESU Delivery
5656

@@ -84,14 +84,14 @@ To create the SQL Server registry, follow these steps:
8484

8585
## Register instances for ESUs
8686

87-
After the **SQL Server registry** resource is deployed, you can choose to register a [single](#single-sql-server-instance) SQL Server instance, or you can register a number of SQL Server instances in [bulk](#multiple-sql-server-instances-in-bulk). It's required that at least one SQL Server instance is registered in the scope of your SQL Server registry in order to download any ESU packages.
87+
After the **SQL Server registry** resource is deployed, you can choose to register a [single](#single-sql-server-instance) SQL Server instance, or you can register a multiple instances of SQL Server instances in [bulk](#multiple-sql-server-instances-in-bulk). It's required that at least one SQL Server instance is registered in the scope of your SQL Server registry in order to download any ESU packages.
8888

8989
### Single SQL Server instance
9090

9191
To register a single SQL Server instance, follow these steps:
9292

9393
1. Sign into the [Azure portal](https://portal.azure.com).
94-
1. Navigate to your **SQL Server registry** resource.
94+
1. Go to your **SQL Server registry** resource.
9595
1. Select **+ Register** from the **Overview** pane:
9696

9797
![Choose register to register a single instance of SQL Server](media/sql-server-extended-security-updates/register-single-sql-server-instance.png)
@@ -123,7 +123,7 @@ Once a SQL Server instance has been registered, the **Security Updates** section
123123
Multiple SQL Server instances can be registered in bulk by uploading a .CSV file. Once your [.CSV file has been formatted correctly](#formatting-requirements-for-csv-file), you can follow these steps to bulk register your SQL Server instances with the SQL Server registry resource:
124124

125125
1. Sign into the [Azure portal](https://portal.azure.com).
126-
1. Navigate to your **SQL Server registry** resource.
126+
1. Go to your **SQL Server registry** resource.
127127
1. Select **Bulk Register** from the **Overview** pane:
128128

129129
![Choose bulk register to register multiple instances of SQL Server](media/sql-server-extended-security-updates/bulk-register-sql-server-instances.png)
@@ -133,8 +133,6 @@ Multiple SQL Server instances can be registered in bulk by uploading a .CSV file
133133
![Upload CSV file to register multiple instances of SQL Server](media/sql-server-extended-security-updates/upload-csv-file-for-bulk-registration.png)
134134

135135

136-
![csv]((media/sql-server-extended-security-updates/upload-csv-file-for-bulk-registration.png)
137-
138136
### Formatting requirements for CSV file
139137
- Values are comma-separated
140138
- Values are not single or double-quoted
@@ -195,7 +193,7 @@ Once your SQL Server instances have been registered with the SQL Server registry
195193
To download ESUs, follow these steps:
196194

197195
1. Sign into the [Azure portal](https://portal.azure.com).
198-
1. Navigate to your **SQL Server registry** resource.
196+
1. Go to your **SQL Server registry** resource.
199197
1. Select **Security Updates** on the navigation pane.
200198

201199
![Check security updates pane for available updates](media/sql-server-extended-security-updates/security-updates-sql-registry.png)
@@ -211,6 +209,7 @@ General frequently asked questions about Extended Security updates can be found
211209
The End of Support date for SQL Server 2008 and 2008 R2 is July 9, 2019.
212210

213211
**What does End of Support mean?**
212+
214213
Microsoft Lifecycle Policy offers 10 years of support (5 years for Mainstream Support and 5 years for Extended Support) for Business and Developer products (such as SQL Server and Windows Server). As per the policy, after the end of the Extended Support period there will be no patches or security updates, which may cause security and compliance issues, and expose customers’ applications and business to serious security risks.
215214

216215
**What editions of SQL Server are eligible for Extended Security Updates?**
@@ -293,7 +292,7 @@ For advice on how to optimize performance for SQL Server on Azure virtual machin
293292

294293
## See also
295294

296-
- [SQL Server 2008 / 2008 R2 lifecycle page](https://support.microsoft.com/en-us/lifecycle/search?alpha=sql%20server%202008)
295+
- [SQL Server 2008 / 2008 R2 lifecycle page](https://support.microsoft.com/lifecycle/search?alpha=sql%20server%202008)
297296
- [SQL Server 2008 / 2008 R2 end of support page](https://aka.ms/sqleos)
298297
- [Extended Security Updates frequently asked questions (FAQ)](https://aka.ms/sqleosfaq)
299298
- [Microsoft Security Response Center (MSRC)](https://portal.msrc.microsoft.com/security-guidance/summary)

docs/sql-server/migrate/index.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,13 +20,13 @@ landingContent:
2020
linkLists:
2121
- linkListType: overview
2222
links:
23-
- text: Database Migration Assistant (DMA)
23+
- text: Data Migration Assistant (DMA)
2424
url: ../../dma/dma-overview.md
2525
- text: Database Experimentation Assistant
2626
url: ../../dea/database-experimentation-assistant-overview.md
2727
- linkListType: learn
2828
links:
29-
- text: Database Migration Assistant
29+
- text: Data Migration Assistant (DMA)
3030
url: /learn/modules/assess-convert-sql-server-databases-using-dma/
3131
- text: Database Experimentation Assistant
3232
url: /learn/modules/test-optimize-sql-server-databases-using-dea/
@@ -63,15 +63,15 @@ landingContent:
6363
links:
6464
- text: Database Migration Service (DMS)
6565
url: /azure/dms/
66-
- text: Database Migration Assistant (DMA)
66+
- text: Data Migration Assistant (DMA)
6767
url: ../../dma/dma-overview.md
6868
- linkListType: concept
6969
links:
7070
- text: Cloud adoption framework
7171
url: /azure/cloud-adoption-framework/migrate/expanded-scope/sql-migration
7272
- linkListType: learn
7373
links:
74-
- text: Database Migration Assistant
74+
- text: Data Migration Assistant (DMA)
7575
url: /learn/modules/assess-convert-sql-server-databases-using-dma/
7676

7777
- title: Resources

docs/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4616,7 +4616,7 @@
46164616
- name: Migrate & load data
46174617
items:
46184618
- name: Migration content
4619-
href: /sql-server/migrate/index.yml
4619+
href: sql-server/migrate/index.yml
46204620
- name: SQL Server Integration Services (SSIS) >
46214621
href: integration-services/index.md
46224622
- name: Bulk Copy Utility (bcp)

0 commit comments

Comments
 (0)