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.
If you don't already have a Google Account (Gmail or G Suite), the first step is to create one. Sign-in to Google Cloud Console (console.cloud.google.com) and create a new project:
Remember the project ID entered above (a unique identifier for your project on Google Cloud Platform). It will be referred to later in this codelab as
Next, you'll need to enable billing in Google Cloud Console in order to use Google Cloud Platform resources like Cloud Datastore and Cloud Storage.
New users of Google Cloud Platform are eligible for a $300 free trial. Running through this codelab shouldn't cost you more than a few dollars, but it could be more if you decide to use more resources or if you leave them running (see the "cleanup" section at the end of this document).
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.
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.
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:
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.
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.