Skip to content

Commit 35365cf

Browse files
authored
Merge pull request #105026 from MicrosoftDocs/release-rebrand-sqldw
Release rebrand sqldw
2 parents 840e51a + 5e90c8f commit 35365cf

File tree

200 files changed

+1412
-1421
lines changed

Some content is hidden

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

200 files changed

+1412
-1421
lines changed

articles/sql-data-warehouse/analyze-your-workload.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,25 @@
11
---
22
title: Analyze your workload
3-
description: Techniques for analyzing query prioritization for your workload in Azure SQL Data Warehouse.
3+
description: Techniques for analyzing query prioritization for your workload in Azure Synapse Analytics.
44
services: sql-data-warehouse
55
author: ronortloff
66
manager: craigg
77
ms.service: sql-data-warehouse
88
ms.topic: conceptual
99
ms.subservice: workload-management
10-
ms.date: 03/13/2019
10+
ms.date: 02/04/2020
1111
ms.author: rortloff
1212
ms.reviewer: jrasnick
13-
ms.custom: seo-lt-2019​
13+
ms.custom: azure-synapse
1414
---
1515

16-
# Analyze your workload in Azure SQL Data Warehouse
16+
# Analyze your workload in Azure Synapse Analytics
1717

18-
Techniques for analyzing your workload in Azure SQL Data Warehouse.
18+
Techniques for analyzing your SQL Analytics workload in Azure Synapse Analytics.
1919

2020
## Resource Classes
2121

22-
SQL Data Warehouse provides resource classes to assign system resources to queries. For more information on resource classes, see [Resource classes & workload management](resource-classes-for-workload-management.md). Queries will wait if the resource class assigned to a query needs more resources than are currently available.
22+
SQL Analytics provides resource classes to assign system resources to queries. For more information on resource classes, see [Resource classes & workload management](resource-classes-for-workload-management.md). Queries will wait if the resource class assigned to a query needs more resources than are currently available.
2323

2424
## Queued query detection and other DMVs
2525

@@ -58,7 +58,7 @@ WHERE r.name IN ('mediumrc','largerc','xlargerc')
5858
;
5959
```
6060

61-
SQL Data Warehouse has the following wait types:
61+
SQL Analytics has the following wait types:
6262

6363
* **LocalQueriesConcurrencyResourceType**: Queries that sit outside of the concurrency slot framework. DMV queries and system functions such as `SELECT @@VERSION` are examples of local queries.
6464
* **UserConcurrencyResourceType**: Queries that sit inside the concurrency slot framework. Queries against end-user tables represent examples that would use this resource type.
@@ -148,4 +148,4 @@ FROM sys.dm_pdw_wait_stats w
148148

149149
## Next steps
150150

151-
For more information about managing database users and security, see [Secure a database in SQL Data Warehouse](sql-data-warehouse-overview-manage-security.md). For more information about how larger resource classes can improve clustered columnstore index quality, see [Rebuilding indexes to improve segment quality](sql-data-warehouse-tables-index.md#rebuilding-indexes-to-improve-segment-quality).
151+
For more information about managing database users and security, see [Secure a database in SQL Analytics](sql-data-warehouse-overview-manage-security.md). For more information about how larger resource classes can improve clustered columnstore index quality, see [Rebuilding indexes to improve segment quality](sql-data-warehouse-tables-index.md#rebuilding-indexes-to-improve-segment-quality).

articles/sql-data-warehouse/backup-and-restore.md

Lines changed: 22 additions & 22 deletions
Large diffs are not rendered by default.

articles/sql-data-warehouse/column-level-security.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,17 @@
11
---
2-
title: What is column-level security for SQL Data Warehouse?
2+
title: What is column-level security for Azure Synapse?
33
description: Column-Level Security allows customers to control access to database table columns based on the user's execution context or group membership, simplifying the design and coding of security in your application, and allowing you to implement restrictions on column access.
44
services: sql-data-warehouse
55
author: julieMSFT
66
manager: craigg
77
ms.service: sql-data-warehouse
88
ms.topic: conceptual
99
ms.subservice: security
10-
ms.date: 04/02/2019
10+
ms.date: 02/05/2020
1111
ms.author: jrasnick
1212
ms.reviewer: igorstan, carlrab
1313
ms.custom: seo-lt-2019
14+
tags: azure-synapse
1415
---
1516

1617
# Column-level Security
@@ -19,7 +20,7 @@ Column-Level Security allows customers to control access to table columns based
1920

2021

2122
> [!VIDEO https://www.youtube.com/embed/OU_ESg0g8r8]
22-
Since this video was posted [Row level Security](/sql/relational-databases/security/row-level-security?toc=%2Fazure%2Fsql-data-warehouse%2Ftoc&view=sql-server-2017) became available for SQL Data Warehouse.
23+
Since this video was posted [Row level Security](/sql/relational-databases/security/row-level-security?toc=%2Fazure%2Fsql-data-warehouse%2Ftoc&view=sql-server-2017) became available for Azure Synapse.
2324

2425
Column-level security simplifies the design and coding of security in your application, allowing you to restrict column access to protect sensitive data. For example, ensuring that specific users can access only certain columns of a table pertinent to their department. The access restriction logic is located in the database tier rather than away from the data in another application tier. The database applies the access restrictions every time data access is attempted from any tier. This restriction makes your security more reliable and robust by reducing the surface area of your overall security system. In addition, column-level security also eliminates the need for introducing views to filter out columns for imposing access restrictions on the users.
2526

0 commit comments

Comments
 (0)