Model Context Protocol (MCP) finally gives AI models a way to access the business data needed to make them really useful at work. CData MCP Servers have the depth and performance to make sure AI has access to all of the answers.
Try them now for free →Migrating data from IBM Cloud Object Storage to Google BigQuery using CData SSIS Components.
Easily push IBM Cloud Object Storage data to Google BigQuery using the CData SSIS Tasks for IBM Cloud Object Storage and Google BigQuery.
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 IBM Cloud Object Storage data to Google BigQuery using the CData SSIS Components for IBM Cloud Object Storage 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:
-
The component represents INTERVAL types as strings. Whenever a query requires an INTERVAL type, it must specify the INTERVAL using the BigQuery SQL INTERVAL format:
YEAR-MONTH DAY HOUR:MINUTE:SECOND.FRACTION
-
For example, the value "5 years and 11 months, minus 10 days and 3 hours and 2.5 seconds" in the correct format is:
5-11 -10 -3:0:0.2.5
-
The component represents INTERVAL types as strings. Whenever a query requires an INTERVAL type, it must specify the INTERVAL using the BigQuery SQL INTERVAL format:
Prerequisites
- Visual Studio 2022
- SQL Server Integration Services Projects extension for Visual Studio 2022
- CData SSIS Components for Google BigQuery
- CData SSIS Components for IBM Cloud Object Storage
Create the project and add components
-
Open Visual Studio and create a new Integration Services Project.
- Add a new Data Flow Task to the Control Flow screen and open the Data Flow Task.
-
Add a CData IBM Cloud Object Storage Source control and a CData GoogleBigQuery Destination control to the data flow task.
Configure the IBM Cloud Object Storage source
Follow the steps below to specify properties required to connect to IBM Cloud Object Storage.
-
Double-click the CData IBM Cloud Object Storage Source to open the source component editor and add a new connection.
-
In the CData IBM Cloud Object Storage Connection Manager, configure the connection properties, then test and save the connection.
Register a New Instance of Cloud Object Storage
If you do not already have Cloud Object Storage in your IBM Cloud account, follow the procedure below to install an instance of SQL Query in your account:
- Log in to your IBM Cloud account.
- Navigate to the page, choose a name for your instance and click Create. You will be redirected to the instance of Cloud Object Storage you just created.
Connecting using OAuth Authentication
There are certain connection properties you need to set before you can connect. You can obtain these as follows:
API Key
To connect with IBM Cloud Object Storage, you need an API Key. You can obtain this as follows:
- Log in to your IBM Cloud account.
- Navigate to the Platform API Keys page.
- On the middle-right corner click "Create an IBM Cloud API Key" to create a new API Key.
- In the pop-up window, specify the API Key name and click "Create". Note the API Key as you can never access it again from the dashboard.
Cloud Object Storage CRN
If you have multiple accounts, specify the CloudObjectStorageCRN explicitly. To find the appropriate value, you can:
- Query the Services view. This will list your IBM Cloud Object Storage instances along with the CRN for each.
- Locate the CRN directly in IBM Cloud. To do so, navigate to your IBM Cloud Dashboard. In the Resource List, Under Storage, select your Cloud Object Storage resource to get its CRN.
Connecting to Data
You can now set the following to connect to data:
- InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
- ApiKey: Set this to your API key which was noted during setup.
- CloudObjectStorageCRN (Optional): Set this to the cloud object storage CRN you want to work with. While the connector attempts to retrieve this automatically, specifying this explicitly is recommended if you have more than Cloud Object Storage account.
When you connect, the connector completes the OAuth process.
- Extracts the access token and authenticates requests.
- Saves OAuth values in OAuthSettingsLocation to be persisted across connections.
-
After saving the connection, select "Table or view" and select the table or view to export into Google BigQuery, then close the CData IBM Cloud Object Storage Source Editor.
Configure the Google BigQuery destination
With the IBM Cloud Object Storage 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.
-
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.
-
After saving the connection, select a table in the Use a Table menu and in the Action menu, select Insert.
-
On the Column Mappings tab, configure the mappings from the input columns to the destination columns.
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.