Google BigQuery is a serverless, highly scalable, and cost-effective data warehouse designed to help organizations turn big data into actionable insights.
The CData SSIS Components enhance SQL Server Integration Services by enabling users to easily import and export data from various sources and destinations.
In this article, we explore the data type mapping considerations when exporting to BigQuery and walk through how to migrate Zuora data to Google BigQuery using the CData SSIS Components for Zuora and BigQuery.
Data Type Mapping
| Google BigQuery Schema |
CData Schema |
|
STRING, GEOGRAPHY, JSON, INTERVAL
|
string
|
|
BYTES
|
binary
|
|
INTEGER
|
long
|
|
FLOAT
|
double
|
|
NUMERIC, BIGNUMERIC
|
decimal
|
|
BOOLEAN
|
bool
|
|
DATE
|
date
|
|
TIME
|
time
|
|
DATETIME, TIMESTAMP
|
datetime
|
|
STRUCT
|
See below
|
|
ARRAY
|
See below
|
STRUCT and ARRAY Types
Google BigQuery supports two kinds of types for storing compound values in a single row, STRUCT and ARRAY. In some places within Google BigQuery, these are also known as RECORD and REPEATED types.
A STRUCT is a fixed-size group of values that are accessed by name and can have different types. The component flattens structs so their fields can be accessed using dotted names. Note that these dotted names must be quoted.
An ARRAY is a group of values with the same type that can have any size. The component treats the array as a single compound value and reports it as a JSON aggregate. These types may be combined such that a STRUCT type contains an ARRAY field, or an ARRAY field is a list of STRUCT values.
Special Considerations
-
Google BigQuery has both DATETIME (no timezone) and TIMESTAMP (with timezone) data types that the CData SSIS Components map to datetime based on the timezone of your local machine.
-
In Google BigQuery, the NUMERIC type supports 38 digits of precision and up to 9 digits after the decimal point, while the BIGNUMERIC type supports 76 digits of precision and up to 38 digits after the decimal point. The CData SSIS Components for Google BigQuery automatically detects the precision/scale, but with the Destination Component users can manually map any high-precision columns.
-
INTERVAL data types:
Prerequisites
Create the project and add components
-
Open Visual Studio and create a new Integration Services Project.
π Create the SSIS project
-
Add a new Data Flow Task to the Control Flow screen and open the Data Flow Task.
-
Add a CData Zuora Source control and a CData GoogleBigQuery Destination control to the data flow task.
π Add the source and destination controls (Salesforce is shown)
Configure the Zuora source
Follow the steps below to specify properties required to connect to Zuora.
-
Double-click the CData Zuora Source to open the source component editor and add a new connection.
π Open the source component editor (Salesforce is shown)
-
In the CData Zuora Connection Manager, configure the connection properties, then test and save the connection.
Zuora uses the OAuth standard to authenticate users. See the online Help documentation for a full OAuth authentication guide.
Configuring Tenant property
In order to create a valid connection with the provider you need to choose one of the Tenant values (USProduction by default) which matches your account configuration. The following is a list with the available options:
- USProduction: Requests sent to https://rest.zuora.com.
- USAPISandbox: Requests sent to https://rest.apisandbox.zuora.com"
- USPerformanceTest: Requests sent to https://rest.pt1.zuora.com"
- EUProduction: Requests sent to https://rest.eu.zuora.com"
- EUSandbox: Requests sent to https://rest.sandbox.eu.zuora.com"
Selecting a Zuora Service
Two Zuora services are available: Data Query and AQuA API. By default ZuoraService is set to AQuADataExport.
DataQuery
The Data Query feature enables you to export data from your Zuora tenant by performing asynchronous, read-only SQL queries.
We recommend to use this service for quick lightweight SQL queries.
Limitations
- The maximum number of input records per table after filters have been applied: 1,000,000
- The maximum number of output records: 100,000
- The maximum number of simultaneous queries submitted for execution per tenant: 5
- The maximum number of queued queries submitted for execution after reaching the limitation of simultaneous queries per tenant: 10
- The maximum processing time for each query in hours: 1
- The maximum size of memory allocated to each query in GB: 2
- The maximum number of indices when using Index Join, in other words, the maximum number of records being returned by the left table based on the unique value used in the WHERE clause when using Index Join: 20,000
AQuADataExport
AQuA API export is designed to export all the records for all the objects ( tables ). AQuA query jobs have the following limitations:
Limitations
- If a query in an AQuA job is executed longer than 8 hours, this job will be killed automatically.
- The killed AQuA job can be retried three times before returned as failed.
π Configure the source connection (Salesforce is shown)
-
After saving the connection, select "Table or view" and select the table or view to export into Google BigQuery, then close the CData Zuora Source Editor.
π Select the table to export (Salesforce is shown)
Configure the Google BigQuery destination
With the Zuora Source configured, we can configure the Google BigQuery connection and map the columns.
-
Double-click the CData Google BigQuery Destination to open the destination component editor and add a new connection.
π Open the destination component editor
-
In the CData GoogleBigQuery Connection Manager, configure the connection properties, then test and save the connection.
-
Google uses the OAuth authentication standard. To access Google APIs on behalf of individual users, you can use the embedded credentials or you can register your own OAuth app.
OAuth also enables you to use a service account to connect on behalf of users in a Google Apps domain. To authenticate with a service account, register an application to obtain the OAuth JWT values.
In addition to the OAuth values, specify the DatasetId and ProjectId. See the "Getting Started" chapter of the help documentation for a guide to using OAuth.
Helpful connection properties
-
QueryPassthrough: When this is set to True, queries are passed through directly to Google BigQuery.
-
ConvertDateTimetoGMT: When this is set to True, the components will convert date-time values to GMT, instead of the local time of the machine.
-
FlattenObjects: By default the component reports each field in a STRUCT column as its own column while the STRUCT column itself is hidden. When this is set to False, the top-level STRUCT is not expanded and is left as its own column. The value of this column is reported as a JSON aggregate.
-
SupportCaseSensitiveTables: When this property is set to true, tables with the same name but different casing will be renamed so they are all reported in the metadata. By default, the provider treats table names as case-insensitive, so if multiple tables have the same name but different casing, only one will be reported in the metadata.
π Configure the destination connection
-
After saving the connection, select a table in the Use a Table menu and in the Action menu, select Insert.
π Choose the destination table
-
On the Column Mappings tab, configure the mappings from the input columns to the destination columns.
π Map the columns (Salesforce is shown)
Run the project
You can now run the project. After the SSIS Task has finished executing, data from your SQL table will be exported to the chosen table.