Select Page

Creating Amazon RDS Instance – SQL Server

Manguirish Sardesai | | June 25, 2018

Microsoft SQL Server can be run in AWS in two different ways:

  1. Running SQL Server on EC2 which is very similar to running SQL Server on any Virtual Machines
  2. Using the Relational Database Service (RDS) provided by AWS

Running SQL Server on Elastic Compute Cloud (EC2) has its own advantages as you can have full control over different parameters, permissions and using SQL server native features. However, running SQL Server on RDS is very simple and quick and you will get the fully managed database experience from AWS relatively at the same cost. Here are the quick step by step instructions on how to create an Amazon RDS Instance of SQL Server.

  1. First, you need to logon to AWS Console and then access the RDS dashboard page from the AWS main menu under the ‘Database’ section. You can then click on “Launch a DB Instance.”
  2. You will get multiple options to select the database engine. Please make sure you select the engine as per business and licensing need. Here you will select “Microsoft SQL Server” and edition “SQL Server Enterprise Edition.”
  3. After selecting engine, the next step you need to select is database instance specifications and settings. Here you select Licensing Model, DB Engine info, Database instance class, Storage under database instance details and Database instance name and Master username/password under settings. There are many settings here but the below needs mention:

    Licensing Model: RDS for SQL Server does not have the Bring your own license model (BYOL) anymore and the only choice you have is to choose the license included option.

    DB Engine Version: You need to select which SQL version needed. Latest available is SQL Server 2017 RTM which is the latest.

    DB Instance Class: Here you select an instance class based on the DB Engine version selected.

    Allocated Storage: Here you need to choose how much maximum storage your instance would need. This can be specified once during set-up and can’t be modified as per the AWS limitations.

  4. Click on Next. It will take you to the Advanced Settings configuration.

    Here you get advanced options like “Network & Security,” “Database Options,” “Backup,” “Monitoring,” “Maintenance” etc.
  5. After all options are selected, click on “Launch DB Instance” and AWS will launch the SQL Server instance for you.
  6. After the AWS instance is created you may encounter issues in registering it. For that you will need to change the inbound rules. You need to modify this under the “security group” section and your network admins should help you with that section.
  7. View the endpoint generated by the RDS Instance. Endpoint is nothing but the address of the SQL Server instance that has just been created and you can use this address in the SQL Server management studio (SSMS) or any other client tool to connect to the SQL Server instance. It has to be noted that the connecting string for the endpoint ends with the port number (1433) of the instance separated by a colon (:). You will have to replace this Colon (:) with a comma when you use this connection string in SSMS.

There you go. You are connected to your first AWS RDS SQL Server Instance.

Subscribe to Our Blog

Never miss a post! Stay up to date with the latest database, application and analytics tips and news. Delivered in a handy bi-weekly update straight to your inbox. You can unsubscribe at any time.

ORA-12154: TNS:could not resolve the connect identifier specified

Most people will encounter this error when their application tries to connect to an Oracle database service, but it can also be raised by one database instance trying to connect to another database service via a database link.

Jeremiah Wilton | March 4, 2009

12c Upgrade Bug with SQL Tuning Advisor

Learn the steps to take on your Oracle upgrade 11.2 to 12.1 if you’re having performance problems. Oracle offers a patch and work around to BUG 20540751.

Megan Elphingstone | March 22, 2017

Scripting Out the Logins, Server Role Assignments, and Server Permissions

Imagine over 100 logins on the source server, you need to migrate them to the destination server. Wouldn’t it be awesome if we could automate the process?

JP Chen | October 1, 2015

Work with Us

Let’s have a conversation about what you need to succeed and how we can help get you there.

CONTACT US

Work for Us

Where do you want to take your career? Explore exciting opportunities to join our team.

EXPLORE JOBS