You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/synapse-analytics/database-designer/overview-database-templates.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,15 @@ ms.reviewer: wiassaf
7
7
ms.service: azure-synapse-analytics
8
8
ms.subservice: database-editor
9
9
ms.topic: overview
10
-
ms.date: 10/16/2023
10
+
ms.date: 02/25/2025
11
11
ms.custom: template-overview
12
12
---
13
13
14
14
# What are Azure Synapse database templates?
15
15
16
16
Data takes many forms as it moves from source systems to data warehouses and data marts with the intent to solve business problems. Database templates can help with the transformation of data into insights.
17
17
18
-
Database templates are a set of business and technical data definitions that are pre-designed to meet the needs of a particular industry. They act as blueprints that provide common elements derived from best practices, government regulations, and the complex data and analytic needs of an industry-specific organization.
18
+
Database templates are a set of business and technical data definitions that are predesigned to meet the needs of a particular industry. They act as blueprints that provide common elements derived from best practices, government regulations, and the complex data and analytic needs of an industry-specific organization.
19
19
20
20
These schema blueprints can be used by organizations to plan, architect, and design data solutions for data governance, reporting, business intelligence, and advanced analytics. The data models provide integrated business-wide information architectures that can help you implement, in a timely and predictable way, a proven industry data architecture.
21
21
@@ -50,7 +50,7 @@ Currently, you can choose from the following database templates in Azure Synapse
50
50
***Freight & Logistics** - For companies that provide freight and logistics services.
51
51
***Fund Management** - For companies that manage investment funds for investors.
52
52
***Genomics** - For companies acquiring and analyzing genomic data about human beings or other species.
53
-
***Government** - For organizations controlling, regulating or providing services to a country/region, state or province, or community.
53
+
***Government** - For organizations controlling, regulating, or providing services to a country/region, state or province, or community.
54
54
***Healthcare Insurance** - For organizations providing insurance to cover healthcare needs (sometimes known as Payors).
55
55
***Healthcare Provider** - For organizations providing healthcare services.
56
56
***Life Insurance & Annuities** - For companies that provide life insurance, sell annuities, or both.
@@ -66,10 +66,10 @@ Currently, you can choose from the following database templates in Azure Synapse
66
66
***Travel Services** - For companies providing booking services for airlines, hotels, car rentals, cruises, and vacation packages.
67
67
***Utilities** - For gas, electric, and water utilities; power generators; and water desalinators.
68
68
***Wireless** - For companies providing a range of wireless telecommunications services.
69
-
69
+
70
70
As emission and carbon management is an important discussion in all industries, so we've included those components in all the available database templates. These components make it easy for companies who need to track and report their direct and indirect greenhouse gas emissions.
71
71
72
-
## Next steps
72
+
## Related content
73
73
74
74
Continue to explore the capabilities of the database designer using the links below.
Copy file name to clipboardExpand all lines: articles/synapse-analytics/security/how-to-review-synapse-rbac-role-assignments.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: meenalsri
5
5
ms.service: azure-synapse-analytics
6
6
ms.topic: how-to
7
7
ms.subservice: security
8
-
ms.date: 3/07/2022
8
+
ms.date: 02/25/2025
9
9
ms.author: mesrivas
10
10
ms.reviewer: whhender, wiassaf
11
11
---
@@ -41,7 +41,7 @@ If a principal is assigned the same role at different scopes, you'll see multipl
41
41
42
42
If a role is assigned to a security group, you'll see the roles explicitly assigned to the group but not roles inherited from parent groups.
43
43
44
-
You can filter the list by principal name or email, and selectively filter the object types, roles, and scopes. enter your name or email alias in the Name filter to see roles assigned to you. Only a Synapse Administrator can change your roles.
44
+
You can filter the list by principal name or email, and selectively filter the object types, roles, and scopes. Enter your name or email alias in the Name filter to see roles assigned to you. Only a Synapse Administrator can change your roles.
45
45
46
46
>[!Important]
47
47
>If you are directly or indirectly a member of a group that is assigned roles, you may have permissions that are not shown.
@@ -51,7 +51,7 @@ You can filter the list by principal name or email, and selectively filter the o
51
51
52
52
If you create a new workspace, you and the workspace MSI service principal are automatically given the Synapse Administrator role at workspace scope.
53
53
54
-
## Next steps
54
+
## Related content
55
55
56
56
Learn [how to manage Synapse RBAC role assignments](./how-to-manage-synapse-rbac-role-assignments.md).
Copy file name to clipboardExpand all lines: articles/synapse-analytics/sql-data-warehouse/cheat-sheet.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Cheat sheet for dedicated SQL pool (formerly SQL DW)
3
3
description: Find links and best practices to quickly build your dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics.
4
4
author: WilliamDAssafMSFT
5
5
ms.author: wiassaf
6
-
ms.date: 11/04/2019
6
+
ms.date: 02/28/2025
7
7
ms.service: azure-synapse-analytics
8
8
ms.subservice: sql-dw
9
9
ms.topic: overview
@@ -48,7 +48,7 @@ Use the following strategies, depending on the table properties:
48
48
|:--- |:--- |:--- |
49
49
| Replicated | * Small dimension tables in a star schema with less than 2 GB of storage after compression (~5x compression) |* Many write transactions are on table (such as insert, upsert, delete, update)<br></br>* You change Data Warehouse Units (DWU) provisioning frequently<br></br>* You only use 2-3 columns but your table has many columns<br></br>* You index a replicated table |
50
50
| Round Robin (default) | * Temporary/staging table<br></br> * No obvious joining key or good candidate column |* Performance is slow due to data movement |
51
-
| Hash | * Fact tables<br></br>* Large dimension tables |* The distribution key cannot be updated |
51
+
| Hash | * Fact tables<br></br>* Large dimension tables |* The distribution key can't be updated |
52
52
53
53
**Tips:**
54
54
@@ -69,7 +69,7 @@ Indexing is helpful for reading tables quickly. There is a unique set of technol
69
69
|:--- |:--- |:--- |
70
70
| Heap | * Staging/temporary table<br></br>* Small tables with small lookups |* Any lookup scans the full table |
71
71
| Clustered index | * Tables with up to 100 million rows<br></br>* Large tables (more than 100 million rows) with only 1-2 columns heavily used |* Used on a replicated table<br></br>* You have complex queries involving multiple join and Group By operations<br></br>* You make updates on the indexed columns: it takes memory |
72
-
| Clustered columnstore index (CCI) (default) | * Large tables (more than 100 million rows) | * Used on a replicated table<br></br>* You make massive update operations on your table<br></br>* You overpartition your table: row groups do not span across different distribution nodes and partitions |
72
+
| Clustered columnstore index (CCI) (default) | * Large tables (more than 100 million rows) | * Used on a replicated table<br></br>* You make massive update operations on your table<br></br>* You overpartition your table: row groups don't span across different distribution nodes and partitions |
73
73
74
74
**Tips:**
75
75
@@ -93,7 +93,7 @@ Learn more about [partitions](sql-data-warehouse-tables-partition.md).
93
93
94
94
## Incremental load
95
95
96
-
If you're going to incrementally load your data, first make sure that you allocate larger resource classes to loading your data. This is particularly important when loading into tables with clustered columnstore indexes. See [resource classes](resource-classes-for-workload-management.md) for further details.
96
+
If you're going to incrementally load your data, first make sure that you allocate larger resource classes to loading your data. This is particularly important when loading into tables with clustered columnstore indexes. See [resource classes](resource-classes-for-workload-management.md) for further details.
97
97
98
98
We recommend using PolyBase and ADF V2 for automating your ELT pipelines into your data warehouse.
99
99
@@ -111,7 +111,7 @@ Learn more about [statistics](sql-data-warehouse-tables-statistics.md).
111
111
112
112
Resource groups are used as a way to allocate memory to queries. If you need more memory to improve query or loading speed, you should allocate higher resource classes. On the flip side, using larger resource classes impacts concurrency. You want to take that into consideration before moving all of your users to a large resource class.
113
113
114
-
If you notice that queries take too long, check that your users do not run in large resource classes. Large resource classes consume many concurrency slots. They can cause other queries to queue up.
114
+
If you notice that queries take too long, check that your users don't run in large resource classes. Large resource classes consume many concurrency slots. They can cause other queries to queue up.
115
115
116
116
Finally, by using Gen2 of [dedicated SQL pool (formerly SQL DW)](sql-data-warehouse-overview-what-is.md), each resource class gets 2.5 times more memory than Gen1.
117
117
@@ -131,6 +131,6 @@ We recommend considering SQL Database and Azure Analysis Services in a hub-and-s
131
131
132
132
Learn more about [typical architectures that take advantage of dedicated SQL pool (formerly SQL DW) in Azure Synapse Analytics](/archive/blogs/sqlcat/common-isv-application-patterns-using-azure-sql-data-warehouse).
133
133
134
-
Deploy in one click your spokes in SQL databases from dedicated SQL pool (formerly SQL DW):
134
+
Deploy your spokes in SQL databases from dedicated SQL pool (formerly SQL DW):
135
135
136
136
[](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FMicrosoft%2Fsql-data-warehouse-samples%2Fmaster%2Farm-templates%2FsqlDwSpokeDbTemplate%2Fazuredeploy.json)
0 commit comments