Connecting Microsoft SQL Server to BigQuery: 2 Easy Methods

Are you looking to perform a detailed analysis of your data without having to disturb the production setup on SQL Server? In that case, moving data from SQL Server to a robust data warehouse like Google BigQuery is the right direction to take.

This article aims to guide you with steps to move data from Microsoft SQL Server to BigQuery, shed light on the common challenges, and assist you in navigating through them. You will explore two popular methods that you can utilize to set up Microsoft SQL Server to BigQuery integration.

Prerequisites

• An active Microsoft SQL Server account.
• An active Google Cloud Platform account.
• Working knowledge of Databases and Data Warehouses.
• Working knowledge of SQL queries.
• Clear idea regarding the type of data to be transferred.

Introduction to Microsoft SQL Server

Microsoft SQL Server, a relational database developed by Microsoft, provides strong core functions to store, manage and retrieve information. Microsoft SQL Server uses SQL(Structured Query Language) to manage the database and query the data in the database. Microsoft SQL Server runs on a central server which allows for concurrent user access. The data collected is stored in the server which is accessed by the RDMS and queried using SQL. Microsoft SQL Server supports various business intelligence operations, transaction processing, and it also provides an end-to-end security system for sensitive business data.

To know more about Microsoft SQL Server, visit this link.

Introduction to Google BigQuery

Google BigQuery is a serverless, cost-effective, highly scalable Data Warehousing platform that has built-in Machine Learning features. Its activities are carried out using the Business Intelligence Engine. It allows rapid SQL queries to be integrated with Google’s infrastructure’s processing capacity to manage business transactions, data across several databases, and access control policies for people viewing and querying data.

Many companies, including UPS, Twitter, and Dow Jones, utilize BigQuery. UPS utilizes BigQuery to forecast the exact volume of packages for its various offerings. Twitter uses BigQuery to assist update adverts and combine millions of data points per second.

To know more about Google BigQuery, visit this link.

Methods to Set Up Microsoft SQL Server to BigQuery Integration

Majorly, there are two ways to migrate your data from Microsoft SQL to BigQuery. They are:

• Method 1: Manual ETL Process to Set Up Microsoft SQL Server to BigQuery Integration
• Method 2: Using Hevo Data to Set Up Microsoft SQL Server to BigQuery Integration

For the scope of this blog post, Method 1 will be covered extensively. Towards the end, you can also find the limitations of this method and ways to overcome them.

Method 1: Manual ETL Process to Set Up Microsoft SQL Server to BigQuery Integration

The steps to execute the custom code are as follows:

• Step 1: Export the Data from SQL Server using SQL Server Management Studio (SSMS)
• Step 2: Upload to Google Cloud Storage
• Step 3: Upload to BigQuery from Google Cloud Storage (GCS)
• Step 4: Update the Target Table in BigQuery

Step 1: Export the Data from SQL Server using SQL Server Management Studio (SSMS)

SQL Server Management Studio(SSMS) is a free tool built by Microsoft to enable a coordinated environment for managing any SQL infrastructure. SSMS is used to query, design, and manage your databases from your local machine. We are going to be using the SSMS to extract our data in Comma Separated Value(CSV) format in the steps below.

• Install SSMS if you don’t have it on your local machine. You can install it here.
• Open SSMS and connect to a Structured Query Language (SQL) instance. From the object explorer window, select a database and right-click on the Tasks sub-menu, and choose the Export data option.
• The welcome page of the Server Import and Export Wizard will be opened. Click the Next icon to proceed to export the required data.

• You will see a window to choose a data source. Select your preferred data source.
• In the Server name dropdown list, select a SQL Server instance.
• In the Authentication section select authentication for the data source connection. Next, from the Database drop-down box, select a database from which data will be copied. Once you have filled the drop-down list select ‘Next’.
• The next window is the choose the destination window. You will need to specify the location from which the data will be copied in the SQL server. Under the destination, the drop-down box selects the Flat File destination item.
• In the File name box, establish the CSV file where the data from the SQL database will be exported to and select the next button.
• The next window you will see is the Specify Table Copy or Query window, choose the Copy data from one or more tables or views to get all the data from the table.

• Next, you’d see a Configure Flat File Destination window, select the table from the source table to export the data to the CSV file you specified earlier.
• At this point your file would have been exported, to view the exported file click on preview. To have a sneak peek of the data you just exported.
• Complete the exportation process by hitting ‘Next’. The save and run package window will pop up, click on ‘Next’.
• The Complete Wizard window will appear next, it will give you an overview of all the choices you made during the exporting process. To complete the exportation process, hit on ‘Finish’.
• The exported CSV file will be found in Local Drive, where you specified for it to be exported.

Step 2: Upload to Google Cloud Storage

After completing the exporting process to your local machine, the next step is to transfer the CSV file to Google Cloud Storage(GCS). There are various ways of achieving this, but for the purpose of this blog post, let’s discuss the following methods.

Method 1: Using Gsutil

gsutil is a GCP tool that uses Python programming language. It gives you access to GCS from the command line. To initiate Gsutil follow this quickstart link. gsutil provides a unique way to upload a file to GCS from your local machine.   To create a bucket in which you copy your file to:

The new bucket created is called my-new-bucket. Your bucket name must be globally unique.   If successful the command returns:

To copy your file to GCS:

Where export.csv is the CSV file you want to copy the new bucket you just created.

Method 2: Using Web console

The web console is another alternative you can use to upload your CSV file to the GCS from your local machine. The steps to use the web console are outlined below.

• First, you will have to log in to your GCP account. Toggle on the hamburger menu which displays a drop-down menu. Select Storage and click on the browser on the left tab.

• In order to store the file that you would upload from your local machine, create a new bucket. Make sure the name chosen for the browser is globally unique.

• The bucket you just created will appear on the window, click on it and select upload files. This action will direct you to your local drive where you will need to choose the CSV file you want to upload to GCS.
• As soon as you start uploading, a progress bar is shown. The bar disappears once the process has been completed. You will be able to find your file in the bucket.

Step 3: Upload Data to BigQuery From GCS

BigQuery is where the data analysis you need will be carried out. Hence you need to upload your data from GCS to BigQuery. There are various methods that you can use to upload your files from GCS to BigQuery. Let’s discuss 2 methods here:

Method 1: Using the Web Console UI

• The first point of call when using the Web UI method is to select BigQuery under the hamburger menu on the GCP home page.

• Select the create a new dataset icon and fill the corresponding drop-down menu.
• Create a new table under the data set you just created to store your CSV file
• In the create table page –> in the source data section: Select GCS to browse your bucket and select the CSV file you uploaded to GCS – Make sure your File Format is set to CSV
  • Fill the destination tab and the destination table
  • Under schema, click on auto detect schema
  • Select create table
• After creating the table, click on the destination table name you created to view your exported data file.

• Using Command Line Interface, the Activate Cloud Shell icon shown below will take you to the command-line interface command-line syntax is shown below.

Your schema can be specified using the Command-Line. an example is shown below

You can also use the auto-detect feature to specify your schema. The code block below explains it.  bq –location=US load –autodetect –source_format=CSV your_dataset.your_table gs://my-new-bucket/data.csv    There are 3 ways to write to an existing table on BigQuery. You can make use of any of them to write to your table. Illustrations of the options are given below  

1. Overwrite the data

2. Append the table

3. Add a new field to the target table. An extra field will be added to the schema.

Step 4: Update the Target Table in BigQuery

GCS acts as a staging area for BigQuery, so when you are using Command-Line to upload to BigQuery, your data will be stored in an intermediate table. The data in the intermediate table will need to be updated for the effect to be shown in the target table. There are two ways to update the target table in BigQuery. I will be explaining both of them below. 1. Update the rows in the final table and insert new rows from the intermediate table

UPDATE final_table t SET t.value = s.value FROM intermediate_data_table s WHERE t.id = s.id;INSERT final_table (id, value) SELECT id, value FROM intermediate_data_table WHERE NOT id IN (SELECT id FROM final_table);

2. Delete all the rows from the final table which are in the intermediate table

Limitations of Manual ETL Process to Set Up Microsoft SQL Server to BigQuery Integration

Businesses need to put systems in place that will enable them to gain the insights they need from their data. These systems have to be seamless and rapid. Using custom ETL scripts has the following limitations that will affect the reliability and speed of these systems:

1. Writing custom code is only ideal if you’re looking to move your data once from Microsoft SQL Server to BigQuery.
2. Custom ETL code does not scale well with stream and real-time data. You will have to write additional code to update your data. This is far from ideal.
3. When there’s a need to transform or encrypt your data, custom ETL code fails as it will require you to add additional processes to your pipeline.
4. Maintaining and managing a running data pipeline such as this will need you to invest heavily in engineering resources.

While writing code to move data from SQL Server to BigQuery looks like a no-brainer, in the beginning, the implementation and management are much more nuanced than that. The process has a high propensity for errors which will, in turn, have a huge impact on the data quality and consistency. 

Method 2: Using Hevo Data to Set Up Microsoft SQL Server to BigQuery Integration

Hevo Data, a No-code Data Pipeline, helps you directly transfer data from Microsoft SQL Server and 100+ sources to Google BigQuery and other Data Warehouses, Databases, BI tools, or a destination of your choice in a completely hassle-free & automated manner. Hevo is fully managed and completely automates the process of not only loading data from your desired source but also enriching the data and transforming it into an analysis-ready form without having to write a single line of code. Its fault-tolerant architecture ensures that the data is handled in a secure, consistent manner with zero data loss.

Hevo Data takes care of all your Data Preprocessing needs and lets you focus on key business activities and draw a much powerful insight on how to generate more leads, retain customers, and take your business to new heights of profitability. It provides a consistent & reliable solution to manage data in real-time and always have analysis-ready data in your desired destination. 

Sign up here for a 14-Day Free Trial!

The steps to load data from Microsoft SQL Server to BigQuery using Hevo Data are as follow:

• Connect your Microsoft SQL Server account to Hevo’s platform. Hevo has an in-built Microsoft SQL Server Integration that connects to your account within minutes.

• Select Google BigQuery as your destination and start moving your data.

With this, you have successfully set up Microsoft SQL Server to BigQuery Integration using Hevo Data.

Here are more reasons to try Hevo:

• Secure: Hevo has a fault-tolerant architecture that ensures that the data is handled in a secure, consistent manner with zero data loss.
• Schema Management: Hevo takes away the tedious task of schema management & automatically detects the schema of incoming data and maps it to the destination schema.
• Minimal Learning: Hevo, with its simple and interactive UI, is extremely simple for new customers to work on and perform operations.
• Hevo Is Built To Scale: As the number of sources and the volume of your data grows, Hevo scales horizontally, handling millions of records per minute with very little latency.
• Incremental Data Load: Hevo allows the transfer of data that has been modified in real-time. This ensures efficient utilization of bandwidth on both ends.
• Live Support: The Hevo team is available round the clock to extend exceptional support to its customers through chat, email, and support calls.
• Live Monitoring: Hevo allows you to monitor the data flow and check where your data is at a particular point in time.

Conclusion

This article gave you a comprehensive guide to setting up Microsoft SQL Server to BigQuery integration using 2 popular methods. It also gave you a brief overview of Microsoft SQL Server and Google BigQuery. There are certain limitations also associated with the custom ETL method. With Hevo, you can achieve simple and efficient Data Replication from Microsoft SQL Server to BigQuery. Hevo can help you move data from not just SQL Server but 100s of additional data sources.

Visit our Website to Explore Hevo

Businesses can use automated platforms like Hevo Data to set this integration and handle the ETL process. It helps you directly transfer data from a source of your choice to a Data Warehouse, Business Intelligence tools, or any other desired destination in a fully automated and secure manner without having to write any code and will provide you a hassle-free experience.

Want to try Hevo? Sign Up for a 14-day free trial and experience the feature-rich Hevo suite first hand. Have a look at our unbeatable pricing, which will help you choose the right plan for you.

Share your experience of loading data from Microsoft SQL Server to BigQuery in the comment section below.