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/data-factory/connector-google-bigquery-legacy.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
@@ -1,7 +1,7 @@
1
1
---
2
-
title: Copy data from Google BigQuery using legacy
2
+
title: Copy data from Google BigQuery V1
3
3
titleSuffix: Azure Data Factory & Azure Synapse
4
-
description: Learn how to copy data from Google BigQuery to supported sink data stores by using a copy activity in a legacy Azure Data Factory or Synapse Analytics pipeline.
4
+
description: Learn how to copy data from Google BigQuery V1 to supported sink data stores by using a copy activity in an Azure Data Factory or Synapse Analytics pipeline.
5
5
ms.author: jianleishen
6
6
author: jianleishen
7
7
ms.subservice: data-movement
@@ -10,7 +10,7 @@ ms.custom: synapse
10
10
ms.date: 01/26/2025
11
11
---
12
12
13
-
# Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics (legacy)
13
+
# Copy data from Google BigQuery V1 using Azure Data Factory or Synapse Analytics
This article outlines how to use Copy Activity in Azure Data Factory and Synapse Analytics pipelines to copy data from Google BigQuery. It builds on the [Copy Activity overview](copy-activity-overview.md) article that presents a general overview of the copy activity.
Copy file name to clipboardExpand all lines: articles/data-factory/connector-google-bigquery.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
@@ -1,7 +1,7 @@
1
1
---
2
-
title: Copy data from Google BigQuery
2
+
title: Copy data from Google BigQuery V2
3
3
titleSuffix: Azure Data Factory & Azure Synapse
4
-
description: Learn how to copy data from Google BigQuery to supported sink data stores by using a copy activity in an Azure Data Factory or Synapse Analytics pipeline.
4
+
description: Learn how to copy data from Google BigQuery V2 to supported sink data stores by using a copy activity in an Azure Data Factory or Synapse Analytics pipeline.
5
5
ms.author: jianleishen
6
6
author: jianleishen
7
7
ms.subservice: data-movement
@@ -10,7 +10,7 @@ ms.custom: synapse
10
10
ms.date: 01/26/2025
11
11
---
12
12
13
-
# Copy data from Google BigQuery using Azure Data Factory or Synapse Analytics
13
+
# Copy data from Google BigQuery V2 using Azure Data Factory or Synapse Analytics
@@ -225,11 +225,11 @@ To learn details about the properties, check [Lookup activity](control-flow-look
225
225
226
226
To upgrade the Google BigQuery connector, create a new Google BigQuery linked service and configure it by referring to [Linked service properties](#linked-service-properties).
227
227
228
-
## Differences between Google BigQuery and Google BigQuery (legacy)
228
+
## <aname="differences-between-google-bigquery-and-google-bigquery-legacy"></a> Differences between Google BigQuery V2 and V1
229
229
230
-
The Google BigQuery connector offers new functionalities and is compatible with most features of Google BigQuery (legacy) connector. The table below shows the feature differences between Google BigQuery and Google BigQuery (legacy).
230
+
The Google BigQuery V2 connector offers new functionalities and is compatible with most features of Google BigQuery V1 connector. The table below shows the feature differences between Google BigQuery V2 and V1.
231
231
232
-
| Google BigQuery | Google BigQuery (legacy)|
232
+
| Google BigQuery V2| Google BigQuery V1|
233
233
| :----------- | :------- |
234
234
| Service authentication is supported by the Azure integration runtime and the self-hosted integration runtime.<br>The properties trustedCertPath, useSystemTrustStore, email and keyFilePath are not supported as they are available on the self-hosted integration runtime only. | Service authentication is only supported by the self-hosted integration runtime. <br>Support trustedCertPath, useSystemTrustStore, email and keyFilePath properties. |
235
235
| The following mappings are used from Google BigQuery data types to interim data types used by the service internally. <br><br>Numeric -> Decimal<br>Timestamp -> DateTimeOffset<br>Datetime -> DatetimeOffset | The following mappings are used from Google BigQuery data types to interim data types used by the service internally. <br><br>Numeric -> String<br>Timestamp -> DateTime<br>Datetime -> DateTime |
Copy file name to clipboardExpand all lines: articles/data-factory/connector-mariadb.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ For a list of data stores that are supported as sources/sinks by the copy activi
33
33
34
34
The service provides a built-in driver to enable connectivity, therefore you don't need to manually install any driver using this connector.
35
35
36
-
This connector currently supports MariaDB of version 10.x, 11.x under the recommended new driver version v2 and 10.0 to 10.5 for the legacy driver version.
36
+
This connector currently supports MariaDB of version 10.x, 11.x under the MariaDB connector version 2.0 and 10.0 to 10.5 for version 1.0.
37
37
38
38
## Prerequisites
39
39
@@ -71,12 +71,12 @@ The following sections provide details about properties that are used to define
71
71
72
72
## Linked service properties
73
73
74
-
If you use the recommended driver version, the following properties are supported for MariaDB linked service:
74
+
If you use version 2.0, the following properties are supported for MariaDB linked service:
75
75
76
76
| Property | Description | Required |
77
77
|:--- |:--- |:--- |
78
78
| type | The type property must be set to: **MariaDB**| Yes |
79
-
| driverVersion | The driver version when you select the recommended driver version. The value is v2. | Yes |
79
+
| driverVersion | The driver version when you select version 2.0. The value is v2. | Yes |
80
80
| server | The name of your MariaDB Server. | Yes |
81
81
| port | The port number to connect to the MariaDB server. | No |
82
82
| database | Your MariaDB database name. | Yes |
@@ -146,7 +146,7 @@ If you use the recommended driver version, the following properties are supporte
146
146
}
147
147
```
148
148
149
-
If you use the legacy driver version, the following properties are supported:
149
+
If you use version 1.0, the following properties are supported:
150
150
151
151
| Property | Description | Required |
152
152
|:--- |:--- |:--- |
@@ -244,7 +244,7 @@ To copy data from MariaDB, set the source type in the copy activity to **MariaDB
244
244
245
245
When copying data from MariaDB, the following mappings are used from MariaDB data types to interim data types used by the service internally. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
246
246
247
-
| MariaDB data type | Interim service data type | Interim service data type (for the legacy driver version) |
247
+
| MariaDB data type | Interim service data type (for version 2.0) | Interim service data type (for version 1.0) |
248
248
|:--- |:--- |:--- |
249
249
|`bigint`|`Int64`|`Int64`|
250
250
|`bigint unsigned`|`Decimal`|`Decimal`|
@@ -296,17 +296,17 @@ To learn details about the properties, check [Lookup activity](control-flow-look
296
296
297
297
Here are steps that help you upgrade your MariaDB connector:
298
298
299
-
1. In **Edit linked service** page, select **Recommended** under **Driver version** and configure the linked service by referring to [Linked service properties](connector-mariadb.md#linked-service-properties).
299
+
1. In **Edit linked service** page, select **2.0** under **Version** and configure the linked service by referring to [Linked service properties](connector-mariadb.md#linked-service-properties).
300
300
301
-
1. The data type mapping for the latest MariaDB linked service is different from that for the legacy version. To learn the latest data type mapping, see [Data type mapping for MariaDB](connector-mariadb.md#data-type-mapping-for-mariadb).
301
+
1. The data type mapping for version 2.0 is different from that for version 1.0. To learn the version 2.0 data type mapping, see [Data type mapping for MariaDB](connector-mariadb.md#data-type-mapping-for-mariadb).
302
302
303
303
1. The latest driver version v2 supports more MariaDB versions. For more information, see [Supported capabilities](connector-mariadb.md#supported-capabilities).
Copy file name to clipboardExpand all lines: articles/data-factory/connector-mysql.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ This MySQL connector is supported for the following capabilities:
35
35
36
36
For a list of data stores that are supported as sources/sinks by the copy activity, see the [Supported data stores](copy-activity-overview.md#supported-data-stores-and-formats) table.
37
37
38
-
This connector supports MySQL version 5.5, 5.6, 5.7, 8.0, 8.1 and 8.2 under the recommended new driver version v2 and 5.6, 5.7 and 8.0 for the legacy driver version.
38
+
This connector supports MySQL version 5.5, 5.6, 5.7, 8.0, 8.1 and 8.2 under the MySQL connector version 2.0 and 5.6, 5.7 and 8.0 for version 1.0.
39
39
40
40
## Prerequisites
41
41
@@ -75,12 +75,12 @@ The following sections provide details about properties that are used to define
75
75
76
76
## Linked service properties
77
77
78
-
If you use the recommended driver version，the following properties are supported for MySQL linked service:
78
+
If you use version 2.0, the following properties are supported for MySQL linked service:
79
79
80
80
| Property | Description | Required |
81
81
|:--- |:--- |:--- |
82
82
| type | The type property must be set to: **MySql**| Yes |
83
-
| driverVersion | The driver version when you select the recommended driver version. The value is v2. | Yes |
83
+
| driverVersion | The driver version when you select version 2.0. The value is v2. | Yes |
84
84
| server | The name of your MySQL Server. | Yes |
85
85
| port | The port number to connect to the MySQL server. |No|
86
86
| database | Your MySQL database name. |Yes|
@@ -93,10 +93,10 @@ If you use the recommended driver version，the following properties are support
93
93
| allowZeroDateTime | Specifying this property value to `true` allows the special "zero" date value of `0000-00-00` to be retrieved from the database. If set to `false` (the default), date columns are returned as DateTime values, which means `0000-00-00` cannot be retrieved. <br><br> MySQL permits you to store a "zero" value of `0000-00-00` as a "dummy date". In some cases, this feature is more convenient than using NULL values, and uses less data and index space. To disallow `0000-00-00` in MySQL, enable the [NO_ZERO_DATE](https://dev.mysql.com/doc/refman/8.4/en/sql-mode.html#sqlmode_no_zero_date) mode. For more information, see this [article](https://dev.mysql.com/doc/refman/8.4/en/date-and-time-types.html).| No |
94
94
| connectionTimeout | The length of time (in seconds) to wait for a connection to the server before terminating the attempt and generating an error. | No |
95
95
| convertZeroDateTime | Set it to `true` to return DateTime.MinValue for date or datetime columns that have disallowed values. | No |
96
-
| guidFormat| Determines which column type (if any) should be read as a GUID. Go to this [article](https://mysqlconnector.net/connection-options/) for the description of each column type by searching this property. <br><br> The recommended version treats Char(36) as GUID type by default for better performance. The connector treats Char(36) fields as GUIDs for easier database handling. This treatment simplifies operations such as inserting, updating, and retrieving GUID values, ensuring they are consistently managed as GUID objects in the application code instead of plain strings. This behavior is particularly useful in scenarios where GUIDs are used as primary keys or unique identifiers and provides better performance. If you don't need this default setting, you can configure `guidFormat=none` in connection property. |No|
96
+
| guidFormat| Determines which column type (if any) should be read as a GUID. Go to this [article](https://mysqlconnector.net/connection-options/) for the description of each column type by searching this property. <br><br> Version 2.0 treats Char(36) as GUID type by default for better performance. The connector treats Char(36) fields as GUIDs for easier database handling. This treatment simplifies operations such as inserting, updating, and retrieving GUID values, ensuring they are consistently managed as GUID objects in the application code instead of plain strings. This behavior is particularly useful in scenarios where GUIDs are used as primary keys or unique identifiers and provides better performance. If you don't need this default setting, you can configure `guidFormat=none` in connection property. |No|
97
97
| sslCert | The path to the client's SSL certificate file in PEM format. SslKey must also be specified. |No|
98
98
| sslKey | The path to the client's SSL private key in PEM format. SslCert must also be specified.| No |
99
-
| treatTinyAsBoolean | When set to true, tinyint(1) values are returned as Boolean. Setting this property to false causes tinyint(1) to be returned as SByte/Byte. <br><br>The recommended version treats tinyint(1) as Boolean type by default. For more information, see this [article](https://dev.mysql.com/doc/refman/8.0/en/numeric-type-syntax.html). To let the connector return tiny as numeric, set `treatTinyAsBoolean=false` in the connection properties.| No |
99
+
| treatTinyAsBoolean | When set to true, tinyint(1) values are returned as Boolean. Setting this property to false causes tinyint(1) to be returned as SByte/Byte. <br><br>Version 2.0 treats tinyint(1) as Boolean type by default. For more information, see this [article](https://dev.mysql.com/doc/refman/8.0/en/numeric-type-syntax.html). To let the connector return tiny as numeric, set `treatTinyAsBoolean=false` in the connection properties.| No |
100
100
101
101
**Example:**
102
102
@@ -158,7 +158,7 @@ If you use the recommended driver version，the following properties are support
158
158
}
159
159
```
160
160
161
-
If you use the legacy driver version, the following properties are supported:
161
+
If you use version 1.0, the following properties are supported:
162
162
163
163
| Property | Description | Required |
164
164
|:--- |:--- |:--- |
@@ -275,7 +275,7 @@ If you were using `RelationalSource` typed source, it is still supported as-is,
275
275
276
276
When copying data from MySQL, the following mappings are used from MySQL data types to interim data types used by the service internally. See [Schema and data type mappings](copy-activity-schema-and-type-mapping.md) to learn about how copy activity maps the source schema and data type to the sink.
277
277
278
-
| MySQL data type | Interim service data type | Interim service data type (for the legacy driver version) |
278
+
| MySQL data type | Interim service data type (for version 2.0)| Interim service data type (for version 1.0) |
279
279
|:--- |:--- |:--- |
280
280
|`bigint`|`Int64`|`Int64`|
281
281
|`bigint unsigned`|`Decimal`|`Decimal`|
@@ -327,29 +327,29 @@ To learn details about the properties, check [Lookup activity](control-flow-look
327
327
328
328
Here are steps that help you upgrade your MySQL connector:
329
329
330
-
1. In **Edit linked service** page, select **Recommended** under **Driver version** and configure the linked service by referring to [Linked service properties](connector-mysql.md#linked-service-properties).
330
+
1. In **Edit linked service** page, select **2.0** under **Version** and configure the linked service by referring to [Linked service properties](connector-mysql.md#linked-service-properties).
331
331
332
-
1. The data type mapping for the latest MySQL linked service is different from that for the legacy version. To learn the latest data type mapping, see [Data type mapping for MySQL](connector-mysql.md#data-type-mapping-for-mysql).
332
+
1. The data type mapping for version 2.0 is different from that for version 1.0. To learn the version 2.0 data type mapping, see [Data type mapping for MySQL](connector-mysql.md#data-type-mapping-for-mysql).
333
333
334
-
1.The latest driver version v2 supports more MySQL versions. For more information, see [Supported capabilities](connector-mysql.md#supported-capabilities).
334
+
1.Version 2.0 supports more MySQL versions. For more information, see [Supported capabilities](connector-mysql.md#supported-capabilities).
335
335
336
-
### Best practices for MySQL connector recommended version
336
+
### <aname="best-practices-for-mysql-connector-recommended-version"></a> Best practices for MySQL connector version 2.0
337
337
338
-
This section introduces best practices for MySQL connector recommended version.
338
+
This section introduces best practices for MySQL connector version 2.0.
339
339
340
340
#### Cannot load SSL key
341
341
342
-
-**Symptoms**: If you are using MySQL connector recommended version with SSL Key as a connection property, you may meet the following error message: `Could not load the client key from your_pem_file: Unrecognized PEM header: -----BEGIN PRIVATE KEY-----`
342
+
-**Symptoms**: If you are using MySQL connector version 2.0 with SSL Key as a connection property, you may meet the following error message: `Could not load the client key from your_pem_file: Unrecognized PEM header: -----BEGIN PRIVATE KEY-----`
343
343
344
-
-**Cause**: The recommended version cannot decrypt the PCKS#8 format.
344
+
-**Cause**: Version 2.0 cannot decrypt the PCKS#8 format.
345
345
346
346
-**Recommendation**: Convert the PEM format to PCKS#1.
0 commit comments