Connect to GMO MakeShop Data as an External Data Source using PolyBase

PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for GMO MakeShop, you get access to your GMO MakeShop data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live GMO MakeShop data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above, and only for Standard SQL Server.

CData Connect Cloud provides a pure SQL Server interface for GMO MakeShop, allowing you to query data from GMO MakeShop without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect Cloud pushes all supported SQL operations (filters, JOINs, etc.) directly to GMO MakeShop, leveraging server-side processing to return the requested GMO MakeShop data quickly.

Configure GMO MakeShop Connectivity for PolyBase

Connectivity to GMO MakeShop from PolyBase is made possible through CData Connect Cloud. To work with GMO MakeShop data from PolyBase, we start by creating and configuring a GMO MakeShop connection.

1. Log into Connect Cloud, click Connections and click Add Connection

2. Select "GMO MakeShop" from the Add Connection panel

3. Enter the necessary authentication properties to connect to GMO MakeShop.

   Configuring Access to GMO MakeShop

   GMO MakeShop requires AccessCode for each API. To obtain MembersAccessCode, OrdersAccessCode, ProductsAccessCode, and ShopId, follow the steps below:

   • Log in to the GMO MakeShop Store Manager and click Create Shop.
   • Click any target connection setting from External System Connection in the left-hand navigation menu. If you cannot find it in the menu, please contact GMO Makeshop.
   • Product Data Connection Settings: Click Issue to retrieve the authentication code and ProductsAccessCode.
   • Order Data Connection Settings: First select Get Order Information > Change Order Information settings. Then click Issue to retrieve the authentication code and OrdersAccessCode.
   • Members Data Connection Settings: Select Get/Post/Update/Delete Members Information settings. Then click Issue to retrieve the authentication code and MembersAccessCode.
   < li>Members Authentication Connection Settings: Click Issue to retrieve the authentication code and ProductsAccessCode.

   Authenticating to GMO MakeShop Account

   Set the following connection properties to connect:

   • ShopId: Set the GMO MakeShop Store ID of the connection destination. The GMO MakeShop Store ID is the same as the ID for login.
   • OrdersAccessCode: Set the orders access code retrieved from Order Data Connection Settings. This property is required to access the Orders table.
   • ProductsAccessCode: Set the products access code retrieved from Product Data Connection Settings. This property is required to access the Products table.
   • MembersAccessCode: Set the members access code retrieved from Members Data Connection Settings. This property is required to access the Members table.
   • MemberAuthenticationCode: Set the member authentication code retrieved from Members Authentication Connection Settings. This property is required to execute MemberAuthenticationConfirm.
   • Password: Specify the password for the GMO MakeShop Store Manager login user. This property is required to execute ProductCategoryRegistrationOrModification, ProductMemberGroupPriceRegistrationOrModification, ProductOptionRegistrationOrModification, and ProductRegistrationOrModification.
   
4. Click Create & Test
5. Navigate to the Permissions tab in the Add GMO MakeShop Connection page and update the User-based permissions.

Add a Personal Access Token

If you are connecting from a service, application, platform, or framework that does not support OAuth authentication, you can create a Personal Access Token (PAT) to use for authentication. Best practices would dictate that you create a separate PAT for each service, to maintain granularity of access.

1. Click on your username at the top right of the Connect Cloud app and click User Profile.
2. On the User Profile page, scroll down to the Personal Access Tokens section and click Create PAT.
3. Give your PAT a name and click Create.

4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

Create an External Data Source for GMO MakeShop Data

After configuring the connection, you need to create a credential database for the external data source.

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to GMO MakeShop data.

NOTE: Set IDENTITY to your Connect Cloud username and set SECRET to your Personal Access Token.

CREATE DATABASE SCOPED CREDENTIAL ConnectCloudCredentials
WITH IDENTITY = 'yourusername', SECRET = 'yourPAT';

Create an External Data Source for GMO MakeShop

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for GMO MakeShop with PolyBase:

CREATE EXTERNAL DATA SOURCE ConnectCloudInstance
WITH ( 
  LOCATION = 'sqlserver://tds.cdata.com:14333',
  PUSHDOWN = ON,
  CREDENTIAL = ConnectCloudCredentials
);

Create External Tables for GMO MakeShop

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to GMO MakeShop data from your SQL Server instance. The table column definitions must match those exposed by CData Connect Cloud. You can use the Data Explorer in Connect Cloud to see the table definition.

Sample CREATE TABLE Statement

Execute a CREATE EXTERNAL TABLE SQL command to create the external table(s), using the collation and setting the LOCATION to three-part notation for the connection, catalog, and table. The statement to create an external table based on a GMO MakeShop Members would look similar to the following.

CREATE EXTERNAL TABLE Members(
  MemberId COLLATE [nvarchar](255) NULL,
  MemberName COLLATE [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='GMOMakeShop1.GMOMakeShop.Members',
  DATA_SOURCE=ConnectCloudInstance
);

Having created external tables for GMO MakeShop in your SQL Server instance, you are now able to query local and remote data simultaneously. To get live data access to 100+ SaaS, Big Data, and NoSQL sources directly from your SQL Server database, try CData Connect Cloud today!