Skip to content

Commit e293276

Browse files
julieMSFTjulieMSFT
committed
upate Azure SQL Data Warehouse to Azure Synapse Analytics
1 parent d91791f commit e293276

29 files changed

Lines changed: 57 additions & 57 deletions

‎docs/azure-data-studio/quickstart-sql-dw.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To complete this quickstart, you need Azure Data Studio, and a dedicated SQL poo
2020

2121
- [Install Azure Data Studio](./download-azure-data-studio.md?view=sql-server-ver15).
2222

23-
If you don't already have a dedicated SQL pool, see [Create a SQL Data Warehouse](/azure/sql-data-warehouse/sql-data-warehouse-get-started-provision).
23+
If you don't already have a dedicated SQL pool, see [Create a dedicated SQL pool](/azure/sql-data-warehouse/sql-data-warehouse-get-started-provision).
2424

2525
Remember the server name, and login credentials!
2626

‎docs/connect/jdbc/connecting-using-azure-active-directory-authentication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,7 @@ The example below contains a simple Java application that connects to Azure SQL
284284

285285
![JDBC_AAD_Token](media/jdbc_aad_token.png)
286286
2. Sign in to your Azure SQL Server's user database as an Azure Active Directory admin and using a T-SQL command
287-
provision a contained database user for your application principal. For more information, see the [Connecting to SQL Database or SQL Data Warehouse By Using Azure Active Directory authentication](/azure/azure-sql/database/authentication-aad-overview)
287+
provision a contained database user for your application principal. For more information, see the [Connecting to SQL Database or Azure Synapse Analytics By Using Azure Active Directory authentication](/azure/azure-sql/database/authentication-aad-overview)
288288
for more details on how to create an Azure Active Directory admin and a contained database user.
289289

290290
```

‎docs/connect/odbc/windows/features-of-the-microsoft-odbc-driver-for-sql-server-on-windows.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The ODBC Driver 13.1 for SQL Server contains all the functionality of the previo
3636

3737
Always Encrypted allows clients to encrypt sensitive data inside client applications and never reveal the encryption keys to SQL Server. An Always Encrypted enabled driver installed on the client computer achieves this by automatically encrypting and decrypting sensitive data in the SQL Server client application. The driver encrypts the data in sensitive columns before passing the data to SQL Server, and automatically rewrites queries so that the semantics to the application are preserved. Similarly, the driver transparently decrypts data stored in encrypted database columns that are contained in query results. For more information, see [Using Always Encrypted with the ODBC Driver](../../../connect/odbc/using-always-encrypted-with-the-odbc-driver.md).
3838

39-
Azure Active Directory allows users, DBA's, and application programmers to use Azure Active Directory authentication as a mechanism of connecting to Microsoft Azure SQL Database and Microsoft SQL Server 2016 by using identities in Azure Active Directory (Azure AD). For more information, see [Using Azure Active Directory with the ODBC Driver](../using-azure-active-directory.md), and [Connecting to SQL Database or SQL Data Warehouse By Using Azure Active Directory Authentication](/azure/sql-database/sql-database-aad-authentication).
39+
Azure Active Directory allows users, DBA's, and application programmers to use Azure Active Directory authentication as a mechanism of connecting to Microsoft Azure SQL Database and Microsoft SQL Server 2016 by using identities in Azure Active Directory (Azure AD). For more information, see [Using Azure Active Directory with the ODBC Driver](../using-azure-active-directory.md), and [Connecting to SQL Database or Azure Synapse Analytics By Using Azure Active Directory Authentication](/azure/sql-database/sql-database-aad-authentication).
4040

4141
## Microsoft ODBC Driver 11 for SQL Server on Windows
4242

‎docs/connect/php/azure-active-directory.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.author: "v-daenge"
1515
# Connect Using Azure Active Directory Authentication
1616
[!INCLUDE[Driver_PHP_Download](../../includes/driver_php_download.md)]
1717

18-
[Azure Active Directory](/azure/active-directory/active-directory-whatis) (Azure AD) is a central user ID management technology that operates as an alternative to [SQL Server authentication](how-to-connect-using-sql-server-authentication.md). Azure AD allows connections to Microsoft Azure SQL Database and SQL Data Warehouse with federated identities in Azure AD using a username and password, Windows Integrated Authentication, or an Azure AD access token. The PHP drivers for SQL Server offer partial support for these features.
18+
[Azure Active Directory](/azure/active-directory/active-directory-whatis) (Azure AD) is a central user ID management technology that operates as an alternative to [SQL Server authentication](how-to-connect-using-sql-server-authentication.md). Azure AD allows connections to Microsoft Azure SQL Database and Azure Synapse Analytics with federated identities in Azure AD using a username and password, Windows Integrated Authentication, or an Azure AD access token. The PHP drivers for SQL Server offer partial support for these features.
1919

2020
To use Azure AD, use the **Authentication** or **AccessToken** keywords (they are mutually exclusive), as shown in the following table. For more technical details, refer to [Using Azure Active Directory with the ODBC Driver](../odbc/using-azure-active-directory.md).
2121

‎docs/integration-services/toc.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1615,7 +1615,7 @@
16151615
href: ../integration-services/load-data-to-from-excel-with-ssis.md
16161616
- name: Load data to SQL Server or SQL Database
16171617
href: ../integration-services/load-data-to-sql-database-with-ssis.md
1618-
- name: Load data to SQL Data Warehouse
1618+
- name: Load data to Azure Synapse Analytics
16191619
href: ../integration-services/load-data-to-sql-data-warehouse.md
16201620

16211621

‎docs/relational-databases/security/authentication-access/determining-effective-database-engine-permissions.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ This article describes how to determine who has permissions to various objects i
4646

4747
Fixed Server Roles and Fixed Database Roles have preconfigured permissions that cannot be changed. To determine who is a member of a fixed server role, execute the following query:
4848
> [!NOTE]
49-
> Does not apply to SQL Database or SQL Data Warehouse where server level permission is not available. The `is_fixed_role` column of `sys.server_principals` was added in SQL Server 2012. It is not needed for older versions of SQL Server.
49+
> Does not apply to SQL Database or Azure Synapse Analytics where server level permission is not available. The `is_fixed_role` column of `sys.server_principals` was added in SQL Server 2012. It is not needed for older versions of SQL Server.
5050
> ```sql
5151
> SELECT SP1.name AS ServerRoleName,
5252
> isnull (SP2.name, 'No members') AS LoginName
@@ -101,7 +101,7 @@ Remember that a Windows user might be a member of more than one Windows group (e
101101

102102
The following query returns a list of the permissions that have been granted or denied at the server level. This query should be executed in the master database.
103103
> [!NOTE]
104-
> Server-level permissions cannot be granted or queried on SQL Database or SQL Data Warehouse.
104+
> Server-level permissions cannot be granted or queried on SQL Database or Azure Synapse Analytics.
105105
> ```sql
106106
> SELECT pr.type_desc, pr.name,
107107
> isnull (pe.state_desc, 'No permission statements') AS state_desc,

‎docs/relational-databases/security/authentication-access/principals-database-engine.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ monikerRange: ">=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-s
3434
# Principals (Database Engine)
3535
[!INCLUDE [SQL Server](../../../includes/applies-to-version/sql-asdb-asdbmi-asa-pdw.md)]
3636

37-
*Principals* are entities that can request [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] resources. Like other components of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] authorization model, principals can be arranged in a hierarchy. The scope of influence of a principal depends on the scope of the definition of the principal: Windows, server, database; and whether the principal is indivisible or a collection. A Windows Login is an example of an indivisible principal, and a Windows Group is an example of a principal that is a collection. Every principal has a security identifier (SID). This topic applies to all version of SQL Server, but there are some restrictions on server-level principals in SQL Database or SQL Data Warehouse.
37+
*Principals* are entities that can request [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] resources. Like other components of the [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] authorization model, principals can be arranged in a hierarchy. The scope of influence of a principal depends on the scope of the definition of the principal: Windows, server, database; and whether the principal is indivisible or a collection. A Windows Login is an example of an indivisible principal, and a Windows Group is an example of a principal that is a collection. Every principal has a security identifier (SID). This topic applies to all version of SQL Server, but there are some restrictions on server-level principals in SQL Database or Azure Synapse Analytics.
3838

3939
## SQL Server-level principals
4040

‎docs/relational-databases/security/authentication-access/server-level-roles.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ monikerRange: ">=aps-pdw-2016||>=sql-server-2016||=sqlallproducts-allversions||>
3636

3737
You can add server-level principals ( [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] logins, Windows accounts, and Windows groups) into server-level roles. Each member of a fixed server role can add other logins to that same role. Members of user-defined server roles cannot add other server principals to the role.
3838
> [!NOTE]
39-
> Server-level permissions are not available in SQL Database or SQL Data Warehouse. For more information about SQL Database, see [Controlling and granting database access.](/azure/sql-database/sql-database-manage-logins)
39+
> Server-level permissions are not available in SQL Database or Azure Synapse Analytics. For more information about SQL Database, see [Controlling and granting database access.](/azure/sql-database/sql-database-manage-logins)
4040
4141
## Fixed Server-Level Roles
4242
The following table shows the fixed server-level roles and their capabilities.

‎docs/relational-databases/security/contained-database-users-making-your-database-portable.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||=azure-sqldw-latest||=sql
3535

3636
In the contained database user model, the login in the master database is not present. Instead, the authentication process occurs at the user database, and the database user in the user database does not have an associated login in the master database. The contained database user model supports both Windows authentication and [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] authentication, and can be used in both [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] and [!INCLUDE[ssSDS](../../includes/sssds-md.md)]. To connect as a contained database user, the connection string must always contain a parameter for the user database so that the [!INCLUDE[ssDE](../../includes/ssde-md.md)] knows which database is responsible for managing the authentication process. The activity of the contained database user is limited to the authenticating database, so when connecting as a contained database user, the database user account must be independently created in each database that the user will need. To change databases, [!INCLUDE[ssSDS](../../includes/sssds-md.md)] users must create a new connection. Contained database users in [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can change databases if an identical user is present in another database.
3737

38-
**Azure:** [!INCLUDE[sqldbesa](../../includes/sqldbesa-md.md)] and [!INCLUDE[ssSDW_md](../../includes/sssdw-md.md)] support Azure Active Directory identities as contained database users. [!INCLUDE[ssSDS_md](../../includes/sssds-md.md)] supports contained database users using [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] authentication, but [!INCLUDE[ssSDW_md](../../includes/sssdw-md.md)] does not. For more information, see [Connecting to SQL Database By Using Azure Active Directory Authentication](/azure/azure-sql/database/authentication-aad-overview). When using Azure Active Directory authentication, connections from SSMS can be made using Active Directory Universal Authentication. Administrators can configure Universal Authentication to require Multi-Factor Authentication, which verifies identity by using a phone call, text message, smart card with pin, or mobile app notification. For more information, see [SSMS support for Azure AD MFA with SQL Database and SQL Data Warehouse](/azure/azure-sql/database/authentication-mfa-ssms-overview).
38+
**Azure:** [!INCLUDE[sqldbesa](../../includes/sqldbesa-md.md)] and [!INCLUDE[ssSDW_md](../../includes/sssdw-md.md)] support Azure Active Directory identities as contained database users. [!INCLUDE[ssSDS_md](../../includes/sssds-md.md)] supports contained database users using [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] authentication, but [!INCLUDE[ssSDW_md](../../includes/sssdw-md.md)] does not. For more information, see [Connecting to SQL Database By Using Azure Active Directory Authentication](/azure/azure-sql/database/authentication-aad-overview). When using Azure Active Directory authentication, connections from SSMS can be made using Active Directory Universal Authentication. Administrators can configure Universal Authentication to require Multi-Factor Authentication, which verifies identity by using a phone call, text message, smart card with pin, or mobile app notification. For more information, see [SSMS support for Azure AD MFA with SQL Database and Azure Synapse Analytics](/azure/azure-sql/database/authentication-mfa-ssms-overview).
3939

4040
For [!INCLUDE[ssSDS](../../includes/sssds-md.md)] and [!INCLUDE[ssSDW_md](../../includes/sssdw-md.md)], since the database name is always required in the connection string, no changes are required to the connection string when switching from the traditional model to the contained database user model. For [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] connections, the name of the database must be added to the connection string, if it is not already present.
4141

‎docs/relational-databases/security/encryption/transparent-data-encryption.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,7 @@ TDE protects data at rest, which is the data and log files. It lets you follow m
4747
>**Related topics:**
4848
>
4949
> - [Transparent Data Encryption with Azure SQL Database](/azure/azure-sql/database/transparent-data-encryption-tde-overview)
50-
> - [Get started with Transparent Data Encryption (TDE) on SQL Data Warehouse](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-encryption-tde-tsql)
50+
> - [Get started with Transparent Data Encryption (TDE) in Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-encryption-tde-tsql)
5151
> - [Move a TDE Protected Database to Another SQL Server](../../../relational-databases/security/encryption/move-a-tde-protected-database-to-another-sql-server.md)
5252
> - [Enable TDE on SQL Server Using EKM](../../../relational-databases/security/encryption/enable-tde-on-sql-server-using-ekm.md)
5353
> - [Use SQL Server Connector with SQL Encryption Features](../../../relational-databases/security/encryption/use-sql-server-connector-with-sql-encryption-features.md)
@@ -320,7 +320,7 @@ You can enable TDE on a database that has In-Memory OLTP objects. In [!INCLUDE[s
320320
## Related content
321321

322322
[Transparent Data Encryption with Azure SQL Database](/azure/azure-sql/database/transparent-data-encryption-tde-overview)
323-
[Get started with Transparent Data Encryption (TDE) on SQL Data Warehouse](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-encryption-tde-tsql)
323+
[Get started with Transparent Data Encryption (TDE) in Azure Synapse Analytics](/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-encryption-tde-tsql)
324324
[SQL Server Encryption](../../../relational-databases/security/encryption/sql-server-encryption.md)
325325
[SQL Server and Database Encryption Keys (Database Engine)](../../../relational-databases/security/encryption/sql-server-and-database-encryption-keys-database-engine.md)
326326

0 commit comments

Comments
 (0)