Skip to content

Commit cf6b467

Browse files
MikeRayMSFTMikeRayMSFT
authored
Merge pull request #26210 from rwestMSFT/rw-0228-clean-and-sort-metadata
Reviewed build report. Merging to allow validation for publish.
2 parents 6a5cbc9 + b8cab63 commit cf6b467

9,952 files changed

Lines changed: 627953 additions & 652329 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/azure-data-studio/connect.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ ms.reviewer: "maghan"
77
ms.date: 11/15/2022
88
ms.service: azure-data-studio
99
ms.topic: "how-to"
10-
ms.custom:
1110
---
1211

1312
# Connect with Azure Data Studio
@@ -62,4 +61,4 @@ If you have previously been connecting to a SQL Server that does not have encryp
6261

6362
## Next steps
6463

65-
- [Quickstart: Use Azure Data Studio to connect and query SQL Server](quickstart-sql-server.md)
64+
- [Quickstart: Use Azure Data Studio to connect and query SQL Server](quickstart-sql-server.md)

‎docs/azure-data-studio/notebooks/notebooks-kqlmagic.md‎

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,8 @@ title: Notebooks with Kqlmagic (Kusto Query Language) in Azure Data Studio
33
description: This tutorial shows how you can create and run Kqlmagic in an Azure Data Studio notebook.
44
author: markingmyname
55
ms.author: maghan
6-
ms.reviewer: ""
76
ms.date: 12/07/2022
87
ms.service: azure-data-studio
9-
ms.subservice: ""
10-
ms.custonm: ""
118
ms.topic: how-to
129
---
1310

‎docs/azure-data-studio/quickstart-mysql.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,9 @@ ms.reviewer: erinstellato
77
ms.date: 10/12/2022
88
ms.service: azure-data-studio
99
ms.topic: quickstart
10-
ms.custom: intro-quickstart, ignite-2022
10+
ms.custom:
11+
- intro-quickstart
12+
- ignite-2022
1113
---
1214

1315
# Quickstart: Use Azure Data Studio to connect and query MySQL (Preview)

‎docs/azure-data-studio/quickstart-postgres.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ ms.reviewer: maghan
77
ms.date: 11/15/2022
88
ms.service: azure-data-studio
99
ms.topic: quickstart
10-
ms.custom:
1110
---
1211

1312
# Quickstart: Use Azure Data Studio to connect and query PostgreSQL

‎docs/connect/oledb/applications/support-policies-for-oledb-driver-for-sql-server.md‎

Lines changed: 70 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -1,72 +1,70 @@
1-
---
2-
title: "Support policies for OLE DB Driver for SQL Server"
3-
description: "Learn about the support policies for OLE DB Driver for SQL Server and what operating systems and SQL database versions are supported with each driver version."
4-
ms.date: "02/14/2023"
5-
ms.service: sql
6-
ms.reviewer: ""
7-
ms.custom: ""
8-
ms.subservice: connectivity
9-
ms.topic: "reference"
10-
author: David-Engel
11-
ms.author: v-davidengel
12-
---
13-
# Support policies for OLE DB Driver for SQL Server
14-
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
15-
16-
[!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
17-
18-
This article discusses how various data-access components can be used with OLE DB Driver for SQL Server.
19-
20-
## SQL version support
21-
22-
OLE DB Driver for SQL Server is tested with and supports connections to the following versions of SQL Server.
23-
24-
| Database version&nbsp;&#8594;<br />&#8595; Driver version | Azure SQL Database | Azure Synapse Analytics | Azure SQL Managed Instance | SQL Server 2022 | SQL Server 2019 | SQL Server 2017 | SQL Server 2016 | SQL Server 2014 | SQL Server 2012 |
25-
|----|---|---|---|---|---|---|---|---|---|
26-
|19.3|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
27-
|19.2|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
28-
|19.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
29-
|19.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
30-
|18.6|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
31-
|18.5|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
32-
|18.4|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
33-
|18.3|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
34-
|18.2|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
35-
|18.1|Yes|Yes|Yes| | |Yes|Yes|Yes|Yes|
36-
|18.0|Yes|Yes|Yes| | |Yes|Yes|Yes|Yes|
37-
38-
## Supported operating system versions
39-
40-
The following table lists which operating systems are supported by OLE DB Driver for SQL Server.
41-
42-
| Operating system&nbsp;&#8594;<br />&#8595; Driver version | Windows Server 2022 | Windows Server 2019 | Windows Server 2016 | Windows Server 2012<sup>1</sup> | Windows Server 2012 R2<sup>2</sup> | Windows 11 | Windows 10 | Windows 8.1<sup>3</sup> |
43-
|----|---|---|---|---|---|---|---|---|
44-
|19.3|Yes|Yes|Yes|Yes|Yes|Yes|Yes| |
45-
|19.2|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
46-
|19.1|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
47-
|19.0|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
48-
|18.6|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
49-
|18.5| |Yes|Yes|Yes|Yes| |Yes|Yes|
50-
|18.4| |Yes|Yes|Yes|Yes| |Yes|Yes|
51-
|18.3| |Yes|Yes|Yes|Yes| |Yes|Yes|
52-
|18.2| |Yes|Yes|Yes|Yes| |Yes|Yes|
53-
|18.1| | |Yes|Yes|Yes| |Yes|Yes|
54-
|18.0| | |Yes|Yes|Yes| |Yes|Yes|
55-
56-
<sup>1</sup> Supported on Windows Server 2012 with [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
57-
<sup>2</sup> Supported on Windows Server 2012 R2 with [April 2014 update](https://go.microsoft.com/fwlink/?linkid=2073785) and [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
58-
<sup>3</sup> Supported on Windows 8.1 with [April 2014 update](https://go.microsoft.com/fwlink/?linkid=2073785) and [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
59-
60-
## ADO support policies
61-
62-
ADO applications can use the SQLOLEDB OLE DB provider that is included with Windows if they don't require any of the features of [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] or later.
63-
64-
ADO applications can use the OLE DB Driver for SQL Server, but if they do so they must specify `DataTypeCompatibility=80` in the connection strings. Only features from [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] are available when `DataTypeCompatibility=80` is present in the connection strings.
65-
66-
## OLE DB support policies
67-
68-
Applications can use the OLE DB provider (SQLOLEDB) included with the Windows operating system. However, that is in maintenance mode and no longer updated. Use the OLE DB Driver for SQL Server (MSOLEDBSQL19 or MSOLEDBSQL) instead.
69-
70-
## See also
71-
72-
[Building applications with OLE DB Driver for SQL Server](building-applications-with-oledb-driver-for-sql-server.md)
1+
---
2+
title: "Support policies for OLE DB Driver for SQL Server"
3+
description: "Learn about the support policies for OLE DB Driver for SQL Server and what operating systems and SQL database versions are supported with each driver version."
4+
author: David-Engel
5+
ms.author: v-davidengel
6+
ms.date: "02/14/2023"
7+
ms.service: sql
8+
ms.subservice: connectivity
9+
ms.topic: "reference"
10+
---
11+
# Support policies for OLE DB Driver for SQL Server
12+
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
13+
14+
[!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
15+
16+
This article discusses how various data-access components can be used with OLE DB Driver for SQL Server.
17+
18+
## SQL version support
19+
20+
OLE DB Driver for SQL Server is tested with and supports connections to the following versions of SQL Server.
21+
22+
| Database version&nbsp;&#8594;<br />&#8595; Driver version | Azure SQL Database | Azure Synapse Analytics | Azure SQL Managed Instance | SQL Server 2022 | SQL Server 2019 | SQL Server 2017 | SQL Server 2016 | SQL Server 2014 | SQL Server 2012 |
23+
|----|---|---|---|---|---|---|---|---|---|
24+
|19.3|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
25+
|19.2|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
26+
|19.1|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
27+
|19.0|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|Yes|
28+
|18.6|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
29+
|18.5|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
30+
|18.4|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
31+
|18.3|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
32+
|18.2|Yes|Yes|Yes| |Yes|Yes|Yes|Yes|Yes|
33+
|18.1|Yes|Yes|Yes| | |Yes|Yes|Yes|Yes|
34+
|18.0|Yes|Yes|Yes| | |Yes|Yes|Yes|Yes|
35+
36+
## Supported operating system versions
37+
38+
The following table lists which operating systems are supported by OLE DB Driver for SQL Server.
39+
40+
| Operating system&nbsp;&#8594;<br />&#8595; Driver version | Windows Server 2022 | Windows Server 2019 | Windows Server 2016 | Windows Server 2012<sup>1</sup> | Windows Server 2012 R2<sup>2</sup> | Windows 11 | Windows 10 | Windows 8.1<sup>3</sup> |
41+
|----|---|---|---|---|---|---|---|---|
42+
|19.3|Yes|Yes|Yes|Yes|Yes|Yes|Yes| |
43+
|19.2|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
44+
|19.1|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
45+
|19.0|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
46+
|18.6|Yes|Yes|Yes|Yes|Yes| |Yes|Yes|
47+
|18.5| |Yes|Yes|Yes|Yes| |Yes|Yes|
48+
|18.4| |Yes|Yes|Yes|Yes| |Yes|Yes|
49+
|18.3| |Yes|Yes|Yes|Yes| |Yes|Yes|
50+
|18.2| |Yes|Yes|Yes|Yes| |Yes|Yes|
51+
|18.1| | |Yes|Yes|Yes| |Yes|Yes|
52+
|18.0| | |Yes|Yes|Yes| |Yes|Yes|
53+
54+
<sup>1</sup> Supported on Windows Server 2012 with [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
55+
<sup>2</sup> Supported on Windows Server 2012 R2 with [April 2014 update](https://go.microsoft.com/fwlink/?linkid=2073785) and [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
56+
<sup>3</sup> Supported on Windows 8.1 with [April 2014 update](https://go.microsoft.com/fwlink/?linkid=2073785) and [KB2999226](https://go.microsoft.com/fwlink/?linkid=2074061).
57+
58+
## ADO support policies
59+
60+
ADO applications can use the SQLOLEDB OLE DB provider that is included with Windows if they don't require any of the features of [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] or later.
61+
62+
ADO applications can use the OLE DB Driver for SQL Server, but if they do so they must specify `DataTypeCompatibility=80` in the connection strings. Only features from [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] are available when `DataTypeCompatibility=80` is present in the connection strings.
63+
64+
## OLE DB support policies
65+
66+
Applications can use the OLE DB provider (SQLOLEDB) included with the Windows operating system. However, that is in maintenance mode and no longer updated. Use the OLE DB Driver for SQL Server (MSOLEDBSQL19 or MSOLEDBSQL) instead.
67+
68+
## See also
69+
70+
[Building applications with OLE DB Driver for SQL Server](building-applications-with-oledb-driver-for-sql-server.md)

‎docs/connect/oledb/features/registry-settings.md‎

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,12 @@
11
---
2+
title: "Registry Settings"
23
description: "Registry Settings"
3-
title: "Registry Settings | Microsoft Docs"
4-
ms.custom: ""
4+
author: David-Engel
5+
ms.author: v-davidengel
56
ms.date: "08/31/2022"
67
ms.service: sql
7-
ms.reviewer: ""
88
ms.subservice: connectivity
99
ms.topic: "reference"
10-
author: David-Engel
11-
ms.author: v-davidengel
1210
---
1311
# Registry settings
1412
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]

‎docs/database-engine/configure-windows/configure-persistent-memory.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Configure persistent memory (PMEM) - Windows
33
description: Learn how to configure persistent memory (PMEM) for SQL Server on Windows, and how to create namespaces for PMEM devices.
4-
author: briancarrig
4+
author: briancarrig
55
ms.author: brcarrig
66
ms.reviewer: mikeray
77
ms.date: 09/21/2022
8-
ms.topic: conceptual
98
ms.service: sql
109
ms.subservice: configuration
10+
ms.topic: conceptual
1111
---
1212

1313
# Configure persistent memory (PMEM) for SQL Server on Windows

‎docs/dma/dma-migrateonpremsqltosqldb.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@ ms.custom:
1212
- intro-migration
1313
helpviewer_keywords:
1414
- "Data Migration Assistant, on-premises SQL Server"
15-
keywords: ""
1615
---
1716

1817
# Migrate on-premises SQL Server or SQL Server on Azure VMs to Azure SQL Database using the Data Migration Assistant

‎docs/dma/dma-migrateserverlogins.md‎

Lines changed: 52 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,52 @@
1-
---
2-
title: "Migrate SQL Server logins with Data Migration Assistant"
3-
description: Migrate SQL Server logins with Data Migration Assistant, including SQL Server upgrades to later versions of the on-premises product or to SQL Server on Azure VMs.
4-
author: ajithkr-ms
5-
ms.author: ajithkr
6-
ms.date: "10/22/2019"
7-
ms.service: sql
8-
ms.subservice: dma
9-
ms.topic: conceptual
10-
ms.custom:
11-
- seo-lt-2019
12-
- intro-migration
13-
helpviewer_keywords:
14-
- "Data Migration Assistant, login migration"
15-
keywords: ""
16-
---
17-
18-
# Migrate SQL Server logins with Data Migration Assistant
19-
20-
This article provides an overview of migrating SQL Server logins using Data Migration Assistant.
21-
22-
> [!IMPORTANT]
23-
> This topic applies to scenarios involving SQL Server upgrades to later versions of the on-premises product or to SQL Server on Azure Virtual Machines.
24-
25-
## Which logins are migrated
26-
27-
- You can migrate the logins based on a Windows principal (such as a domain user or a Windows domain group). You can also migrate logins created based on SQL authentication, also called SQL Server logins.
28-
29-
- Data Migration Assistant currently doesn't support the logins associated with a stand-alone security certificate (logins mapped to certificate), a stand-alone asymmetric key (logins mapped to asymmetric key), and logins mapped to credentials.
30-
31-
- Data Migration Assistant doesn't move the **sa** login and server principles with names enclosed by double hash marks (\#\#), which are for internal use only.
32-
33-
- By default, Data Migration Assistant selects all the qualified logins to migrate. Optionally, you can select specific logins to migrate. When Data Migration Assistant migrates all qualified logins, the login-user mapping remains intact in the databases that are migrated.
34-
35-
If you plan to migrate specific logins, make sure to select the logins that are mapped to one or more users in the databases selected for migration.
36-
37-
- As part of login migration, Data Migration Assistant also moves user-defined server roles and adds server-level permissions to the user-defined server roles. The owner of the role will be set to **sa** principal.
38-
39-
## During and after migration
40-
41-
- As part of login migration, Data Migration Assistant assigns the permissions to securables on the target SQL Server as they exist on the source SQL Server.
42-
43-
If the login already exists on the target SQL Server, Data Migration Assistant migrates only the permissions assigned to securables and won't re-create the whole login.
44-
45-
- Data Migration Assistant makes the best effort to map the login to database users if the login already exists on the target server.
46-
47-
- It's recommended that you review the migration results to understand the overall status of the login migration and any recommended post-migration actions.
48-
49-
## Resources
50-
51-
[Data Migration Assistant (DMA)](../dma/dma-overview.md)
52-
53-
[Data Migration Assistant: Configuration settings](../dma/dma-configurationsettings.md)
1+
---
2+
title: "Migrate SQL Server logins with Data Migration Assistant"
3+
description: Migrate SQL Server logins with Data Migration Assistant, including SQL Server upgrades to later versions of the on-premises product or to SQL Server on Azure VMs.
4+
author: ajithkr-ms
5+
ms.author: ajithkr
6+
ms.date: "10/22/2019"
7+
ms.service: sql
8+
ms.subservice: dma
9+
ms.topic: conceptual
10+
ms.custom:
11+
- seo-lt-2019
12+
- intro-migration
13+
helpviewer_keywords:
14+
- "Data Migration Assistant, login migration"
15+
---
16+
17+
# Migrate SQL Server logins with Data Migration Assistant
18+
19+
This article provides an overview of migrating SQL Server logins using Data Migration Assistant.
20+
21+
> [!IMPORTANT]
22+
> This topic applies to scenarios involving SQL Server upgrades to later versions of the on-premises product or to SQL Server on Azure Virtual Machines.
23+
24+
## Which logins are migrated
25+
26+
- You can migrate the logins based on a Windows principal (such as a domain user or a Windows domain group). You can also migrate logins created based on SQL authentication, also called SQL Server logins.
27+
28+
- Data Migration Assistant currently doesn't support the logins associated with a stand-alone security certificate (logins mapped to certificate), a stand-alone asymmetric key (logins mapped to asymmetric key), and logins mapped to credentials.
29+
30+
- Data Migration Assistant doesn't move the **sa** login and server principles with names enclosed by double hash marks (\#\#), which are for internal use only.
31+
32+
- By default, Data Migration Assistant selects all the qualified logins to migrate. Optionally, you can select specific logins to migrate. When Data Migration Assistant migrates all qualified logins, the login-user mapping remains intact in the databases that are migrated.
33+
34+
If you plan to migrate specific logins, make sure to select the logins that are mapped to one or more users in the databases selected for migration.
35+
36+
- As part of login migration, Data Migration Assistant also moves user-defined server roles and adds server-level permissions to the user-defined server roles. The owner of the role will be set to **sa** principal.
37+
38+
## During and after migration
39+
40+
- As part of login migration, Data Migration Assistant assigns the permissions to securables on the target SQL Server as they exist on the source SQL Server.
41+
42+
If the login already exists on the target SQL Server, Data Migration Assistant migrates only the permissions assigned to securables and won't re-create the whole login.
43+
44+
- Data Migration Assistant makes the best effort to map the login to database users if the login already exists on the target server.
45+
46+
- It's recommended that you review the migration results to understand the overall status of the login migration and any recommended post-migration actions.
47+
48+
## Resources
49+
50+
[Data Migration Assistant (DMA)](../dma/dma-overview.md)
51+
52+
[Data Migration Assistant: Configuration settings](../dma/dma-configurationsettings.md)

‎docs/dma/dma-whats-new.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.topic: conceptual
1111
ms.custom: intro-whats-new
1212
helpviewer_keywords:
1313
- "Data Migration Assistant, new features"
14-
keywords: ""
1514
---
1615

1716
# What's new in Data Migration Assistant

0 commit comments

Comments
 (0)