Skip to content

Commit 33372dc

Browse files
anshul82-msanshul82-ms
committed
commit
1 parent 294e9be commit 33372dc

3 files changed

Lines changed: 132 additions & 0 deletions

File tree

‎docs/tools/synapse-pathway/azure-synapse-pathway-overview.md‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
title: Azure Synapse Pathway overview
3+
description: This doc describes what is Azure Synapse Pathway, why do you need one and how does it work.
4+
author: anshul82-ms
5+
ms.author: anrampal
6+
ms.topic: overview #Required; leave this attribute/value as-is.
7+
ms.date: 02/22/2020
8+
ms.custom: template-overview #Required; leave this attribute/value as-is.
9+
---
10+
11+
<!--
12+
Remove all the comments in this template before you sign-off or merge to the
13+
main branch.
14+
-->
15+
16+
<!--
17+
This template provides the basic structure of a service/product overview article.
18+
See the [overview guidance](contribute-how-write-overview.md) in the contributor guide.
19+
20+
To provide feedback on this template contact
21+
[the templates workgroup](mailto:templateswg@microsoft.com).
22+
-->
23+
24+
<!-- 1. H1
25+
Required. Set expectations for what the content covers, so customers know the
26+
content meets their needs. H1 format is # What is <product/service>?
27+
-->
28+
29+
# Azure Synapse Pathway
30+
31+
32+
33+
<!-- 2. Introductory paragraph
34+
Required. Lead with a light intro that describes what the article covers. Answer the
35+
fundamental “why would I want to know this?” question. Keep it short.
36+
-->
37+
38+
39+
40+
<!-- 3. H2s
41+
Required. Give each H2 a heading that sets expectations for the content that follows.
42+
Follow the H2 headings with a sentence about how the section contributes to the whole.
43+
-->
44+
45+
## Overview
46+
47+
As customers consider **modernizing their data warehouse systems**, one of the critical blockers they face is translating their SQL code written and optimized for their current system to be optimized for the new system they want to migrate to.
48+
49+
Organizations worldwide want to modernize their analytics platform to enjoy both TCO and innovation benefits. However, customers have invested thousands of working hours, millions of dollars, and written tens of thousands of lines of code for their data warehouse.
50+
To translate this critical SQL code, customers have to **either manually rewrite existing SQL code or invest large amounts of their budget for an outside practice to rewrite or convert their code**. That’s why we are investing in tolling to help accelerate the migration process without upfront cost.
51+
52+
**Azure Synapse Pathway (ASP)** helps you upgrade to a modern cloud data warehouse platform by automating the code translation of your existing data warehouse to fast track your migration to Azure Synapse Analytics.
53+
54+
![Azure Synapse pathway overview.](./media/pathway-overview/synapse-pathway-overview.png)
55+
56+
ASP translates Data Definition Language (DDL) and Data Manipulation Language (DML) statements into T-SQL compliant language that is compatible with Azure Synapse SQL.
57+
58+
## Behind the scenes
59+
<!-- add your content here -->
60+
61+
## Install ASP
62+
To install ASP, download the latest version of the tool from the [Microsoft Download Center](https://aka.ms/asp-download), and then run the **AzureSynapsePathway.msi** file.
63+
64+
## Supported sources
65+
- **IBM Netezza** : Azure Synapse Pathway supports code conversion for database, schemas, tables. DDL statements like create & drop are supported. Function translation is also supported.
66+
67+
- **Microsoft SQL Server**
68+
- **Teradata Vantage**
69+
- **Snowflake**
70+
71+
> [!NOTE]
72+
Check [release notes](..) for new sources added as well as feature additions.
73+
74+
75+
## Frequently asked questions
76+
Please review the [FAQ Page](..) for additional queries on Azure Synapse Pathway
77+
78+
## Next steps
79+
<!-- Add a context sentence for the following links -->
80+
- [Run your first translation with Azure Synapse Pathway](contribute-how-to-write-overview.md)
81+
- [Announcement Blog](links-how-to.md)
82+
83+
<!--
84+
Remove all the comments in this template before you sign-off or merge to the
85+
main branch.
86+
-->

‎docs/tools/synapse-pathway/media/pathway-overview/synapse-pathway-overview.PNG‎

136 KB
Loading

‎docs/tools/synapse-pathway/pathway-faq.md‎

Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: Azure Synapse Pathway FAQ
3+
description: This doc answers the most frequently asked questions.
4+
author: anshul82-ms
5+
ms.author: anrampal
6+
ms.topic: overview #Required; leave this attribute/value as-is.
7+
ms.date: 02/22/2020
8+
ms.custom: template-overview #Required; leave this attribute/value as-is.
9+
---
10+
11+
<!--
12+
Remove all the comments in this template before you sign-off or merge to the
13+
main branch.
14+
-->
15+
16+
<!--
17+
This template provides the basic structure of a service/product overview article.
18+
See the [overview guidance](contribute-how-write-overview.md) in the contributor guide.
19+
20+
To provide feedback on this template contact
21+
[the templates workgroup](mailto:templateswg@microsoft.com).
22+
-->
23+
24+
<!-- 1. H1
25+
Required. Set expectations for what the content covers, so customers know the
26+
content meets their needs. H1 format is # What is <product/service>?
27+
-->
28+
29+
# Azure Synapse Pathway
30+
31+
32+
33+
<!-- 2. Introductory paragraph
34+
Required. Lead with a light intro that describes what the article covers. Answer the
35+
fundamental “why would I want to know this?” question. Keep it short.
36+
-->
37+
38+
39+
40+
<!-- 3. H2s
41+
Required. Give each H2 a heading that sets expectations for the content that follows.
42+
Follow the H2 headings with a sentence about how the section contributes to the whole.
43+
-->
44+
45+
## Overview
46+

0 commit comments

Comments
 (0)