Sunday, 17 July 2016

Deploy or Create SQL server 2016 on the Azure using Windows Server 2012 DataCenter

Today we are showing you about how to Deploy SQL server 2016 on the Azure
We are creating with our Azure subscription, if you don't have an Azure subscription, you can create a free account  in just a couple of minutes.

  • Login to the Azure portal site using your subscription id and password

  • Once login you will be on Portal page of Azure.
  • Click on new>Virtual machines>Select server
  • On the Azure portal, click New. The portal opens the new blade. The SQL Server VM resources are in the Virtual Machines group of the Marketplace.

  • Choose the VM image from the marketplace
Currently we are creating Virtual server (SQL server 2016 RTM on MS windows server 2012 Datacenter)

  • On the Hub menu, click New > Virtual Machines > SQL server 2016

  • Under Select a deployment model, verify that Resource Manager is selected. Resource Manager is the recommended deployment model for new virtual machines. Click Create.

2. Configure basic settings
On the Basics blade, provide the following information:
  • Enter a unique virtual machine Name.
  • Specify a User name for the local administrator account on the VM. This account is also added to the SQL Server sysadmin fixed server role.
  • Provide a strong Password.
  • In the Resource group box, type a name for a new resource group. Alternatively, to use an existing resource group click select existing. A resource group is a collection of related resources in Azure (virtual machines, storage accounts, virtual networks, etc.).
  • Select a Location for this deployment.
  • Click OK to save the settings.

Below is the screen shot for above configuration:
2. Choose virtual machine size
  • On the Size step, choose a virtual machine size in the Choose a size blade. The blade initially displays recommended machine sizes based on the template you selected. It also estimates the monthly cost to run the VM.
  • Here choose you size of server as required for your production

3. Here we will do some setting modification (In our case we are leaving default)
4. Configure SQL server settings
  • On the SQL Server settings blade, configure specific settings and optimizations for SQL Server.  Here we need to defined how we are going to access the server so highlighted we need to select as per our requirement
  • Storage configuration and patch time we can check by clicking on the page and selecting defined option

5. Review the summary

  • On the Summary blade, review the summary and click OK to create SQL Server, resource group, and resources specified for this VM.
  • You can monitor the deployment from the azure portal. The Notifications button at the top of the screen shows basic status of the deployment.

  • Once we will click on ok, Server deployment will start. Probably it will take 10 minutes to complete the installation.

Here we go now we have all set and installed First SQL server on Azure site.
  • After the Azure VM is built, the icon for the VM appears on your Azure dashboard. You can also find it by browsing your existing virtual machines. Click on your new SQL virtual machine. A Virtual machine blade displays your virtual machine details.
  • At the top of the Virtual machine blade, click Connect.
  • The browser downloads an RDP file for the VM. Open the RDP file. 

  • The Remote Desktop Connection notifies you that the publisher of this remote connection cannot be identified. Click Connect to continue.
  • In the Windows Security dialog, click Use another account.
  • For User name type <user name>, where is the user name that you specified when you configured the VM. You have to add an initial backslash before the name.
  • Type the Password that you previously configured for this VM, and then click OK to connect.

  • If another Remote Desktop Connection dialog asks you whether to connect, click Yes.
  • After you connect to the SQL Server virtual machine, you can launch SQL Server Management Studio and connect with Windows Authentication using your local administrator credentials

Now all set, we are able to work on the SQL server using RDP file from anywhere
  • Here we can monitor our server, come back to Azure portal page select VM and see down to blade page, here it will visualize about usage or RAM and CPU


No comments:

Post a Comment