Google Compute Engine lets you create and run virtual machines on Google infrastructure. There is a catalog of public application images, including a variety of Microsoft SQL Server versions and Windows versions.

Follow along with this lab to learn how to create a virtual machine with Microsoft SQL Server installed. You'll also create a Windows user and password and learn how to connect to the Windows Server via remote desktop.

What you'll learn

What you'll need

How will you use this tutorial?

Read it through only Read it and complete the exercises

How would rate your experience with Google Cloud Platform?

Novice Intermediate Proficient

Codelab-at-a-conference setup

Conference codelab instructors will provide you with a temporary account with existing projects, so you do not need to worry about enabling billing or any cost associated with running this codelab. Note that all these accounts will be disabled once the codelab is over.

Once you have received a temporary username / password from the instructor, log into Google Cloud Console:

Here's what you should see once logged in :

Note the project ID you were assigned ( "codelab-test003" in the screenshot above). It will be referred to later in this codelab as PROJECT_ID.

In this section, you will learn how to create a new Google Compute Engine virtual machine instance running Microsoft SQL Server from Google Cloud Console.

Log into Google Cloud Console

Navigate to Google Cloud Console from another browser tab or window. Use the login credentials you received when you signed up for Google Cloud Platform or those given to you by the lab instructor.

Navigate to Compute Engine

In Google Cloud Console, click the Menu icon for Products & services in the top left of the screen:

Then click Compute Engine:

Compute Engine may take a few minutes to initialize.

Then, click Create Instance.

Next, name the new instance ‘sqlserver-codelab':

Choose a zone near you:

Click Change to change the boot disk:

Click Application images:

Choose SQL Server 2016 Web on Windows Server 2016

At the bottom of the window, click Select:

Click Create:

This will take you to a new page where you can new instance being created. A checked green circleappears when the instance is ready.

Note that you will be able to remote desktop (RDP) into the machine from this page, but not before creating a Windows user and password.

You need to remote desktop (RDP) to the Windows instance to configure SQL Server. Before you can RDP into the Windows instance, you must first create a Windows user and password. To create a Windows user and password, first click the name of your instance sqlserver-codelab to see the instance details.

Then, select Create or reset Windows password.

This will open a new window where you can create a user. Keep the default and select Set. After a few seconds, you should have a New Windows password dialog with the newly created password. Click the rectangles to copy the password.

It's time to RDP into the Windows Server. There are two different ways to do this, depending on whether or not you are on Windows. Let's go through them both.

If you are not on Windows but are using Chrome, you can RDP directly from the browser using the Chrome RDP for Google Cloud Platform extension. Click on RDP to connect.

This prompts you to install the Chrome RDP Extension. Once it is installed, it opens up a login page where you can use your Windows username and password to log in.


Alternatively, if you are on a Windows machine, download the RDP file by selecting it from the RDP menu.

On Windows, simply double click the RDP file and log in using the Windows user and password.

Inside your remote desktop window, click the Start menu, and type Sql. Then, click Microsoft SQL Server Management Studio.

Microsoft SQL Server Management Studio launches, showing you a Connect to Server window. Click Connect.

Then, use the Object Explorer window to examine your new database:

Google Compute Engine is the foundation to Google Cloud Platform's Infrastructure-as-a-Service. As you've seen, application images make it easy to run Microsoft SQL Server.

Clean up (Optional)

You can shut down the VM instance to save on costs. You can either delete the instances or simply stop them. Keep in mind that stopped instances still incur storage costs.

What we've covered

Next Steps