Skip to content

Commit 782f24e

Browse files
committed
Update Tip content
1 parent 17cb535 commit 782f24e

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

articles/data-factory/connector-azure-sql-database.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -757,16 +757,16 @@ Settings specific to Azure SQL Database are available in the **Source Options**
757757
**Query**: If you select Query in the input field, enter a SQL query for your source. This setting overrides any table that you've chosen in the dataset. **Order By** clauses aren't supported here, but you can set a full SELECT FROM statement. You can also use user-defined table functions. **select * from udfGetData()** is a UDF in SQL that returns a table. This query will produce a source table that you can use in your data flow. Using queries is also a great way to reduce rows for testing or for lookups.
758758

759759
> [!TIP]
760-
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTE cannot do this.
761-
>To use CTE, you need to create a stored procedure using the following query:
760+
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTEs cannot do this.
761+
>To use CTEs, you need to create a stored procedure using the following query:
762762
>```SQL
763763
> CREATE PROC CTESP @query nvarchar(max)
764764
> AS
765765
> BEGIN
766766
> EXECUTE sp_executesql @query;
767767
> END
768768
>```
769-
>Then use the **Stored procedure** mode in the source transformation of mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTE as expected.
769+
>Then use the **Stored procedure** mode in the source transformation of the mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTEs as expected.
770770

771771
**Stored procedure**: Choose this option if you wish to generate a projection and source data from a stored procedure that is executed from your source database. You can type in the schema, procedure name, and parameters, or click on Refresh to ask the service to discover the schemas and procedure names. Then you can click on Import to import all procedure parameters using the form ``@paraName``.
772772

articles/data-factory/connector-azure-sql-managed-instance.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -766,16 +766,16 @@ The below table lists the properties supported by Azure SQL Managed Instance sou
766766
| Isolation Level | Choose one of the following isolation levels:<br>- Read Committed<br>- Read Uncommitted (default)<br>- Repeatable Read<br>- Serializable<br>- None (ignore isolation level) | No | <small>READ_COMMITTED<br/>READ_UNCOMMITTED<br/>REPEATABLE_READ<br/>SERIALIZABLE<br/>NONE</small> |isolationLevel |
767767

768768
> [!TIP]
769-
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTE cannot do this.
770-
>To use CTE, you need to create a stored procedure using the following query:
769+
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTEs cannot do this.
770+
>To use CTEs, you need to create a stored procedure using the following query:
771771
>```SQL
772772
> CREATE PROC CTESP @query nvarchar(max)
773773
> AS
774774
> BEGIN
775775
> EXECUTE sp_executesql @query;
776776
> END
777777
>```
778-
>Then use the **Stored procedure** mode in the source transformation of mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTE as expected.
778+
>Then use the **Stored procedure** mode in the source transformation of the mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTEs as expected.
779779

780780
#### Azure SQL Managed Instance source script example
781781

articles/data-factory/connector-sql-server.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -641,16 +641,16 @@ The below table lists the properties supported by SQL Server source. You can edi
641641
| Isolation Level | Choose one of the following isolation levels:<br>- Read Committed<br>- Read Uncommitted (default)<br>- Repeatable Read<br>- Serializable<br>- None (ignore isolation level) | No | <small>READ_COMMITTED<br/>READ_UNCOMMITTED<br/>REPEATABLE_READ<br/>SERIALIZABLE<br/>NONE</small> |isolationLevel |
642642

643643
> [!TIP]
644-
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTE cannot do this.
645-
>To use CTE, you need to create a stored procedure using the following query:
644+
> The [common table expression (CTE)](/sql/t-sql/queries/with-common-table-expression-transact-sql?view=sql-server-ver15&preserve-view=true) in SQL is not supported in the mapping data flow **Query** mode, because the prerequisite of using this mode is that queries can be used in the SQL query FROM clause but CTEs cannot do this.
645+
>To use CTEs, you need to create a stored procedure using the following query:
646646
>```SQL
647647
> CREATE PROC CTESP @query nvarchar(max)
648648
> AS
649649
> BEGIN
650650
> EXECUTE sp_executesql @query;
651651
> END
652652
>```
653-
>Then use the **Stored procedure** mode in the source transformation of mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTE as expected.
653+
>Then use the **Stored procedure** mode in the source transformation of the mapping data flow and set the `@query` as `with CTE as (select 'test' as a) select * from CTE`. Then you can use CTEs as expected.
654654

655655
#### SQL Server source script example
656656

0 commit comments

Comments
 (0)