Cloud DB for MSSQL scenario

Available in Classic and VPC

NAVER Cloud Platform's Cloud DB for MSSQL easily and quickly builds MSSQL servers in cloud environments, and operates and manages them to enable stable cache service. The full sequence for utilizing NAVER Cloud Platform's Cloud DB for MSSQL is as follows.

The descriptions for each step are as follows.

1. Create application server
2. Set access environment
3. Test application server connection
4. Create MSSQL Server
5. Set ACG
6. Test MSSQL Server connection

1. Create application server

First, create an application server (app server) that will communicate with the MSSQL server to be created from Cloud DB for MSSQL of the NAVER Cloud Platform console. Currently, Cloud DB for MSSQL is only accessible within NAVER Cloud Platform. Thus, the application server must also reside in NAVER Cloud Platform. The application server (app server) can be created from the Services > Server menu on the NAVER Cloud Platform console. You can refer to the following guide:

• Getting started with server

2. Set access environment

Once you've completed creating an application server, set up an access environment so that users can access the application server. You have two ways of setting the access environment, which are described as follows:

• Set up access using the port forwarding of NAVER Cloud Platform (Classic environment)
• Set up access to a private domain using the public IP of NAVER Cloud Platform (VPC environment)
  For access settings using the public IP, you need to check the admin (root) password required for the server access, using the Get admin password feature.

You can refer to the following guide:

• Checking server information and managing server guide

3. Test application server connection

Once you complete setting up the access environment, use remote desktop connection to test if you can connect to the application server properly. You can refer to the following guide:

• Getting started with Cloud DB for MSSQL

4. Create MSSQL server

After you complete testing the application server connection, create an MSSQL server that will communicate with the application server. The MSSQL server can be created from the Services > Database > Cloud DB for MSSQL menu of the NAVER Cloud Platform console without a separate service subscription request. You can refer to the following guide:

• Getting started with Cloud DB for MSSQL

Server redundancy configuration

To prevent data loss and minimize service impact if failures occur, you can set up server redundancy. When you create a principal server and a mirror server, Cloud DB for MSSQL provides a feature that performs an automatic failover to the mirror server when a failure occurs in the principal server. Since the redundancy is provided in the DNS method, no additional application change is required.

To configure server redundancy, click and select Support high availability when creating the MSSQL server.

Manage monitoring and event

For MSSQL servers that have been created and are in operation, you can check monitoring for server performance and operating system status as well as occurred events, and manage them for stable cache service from the NAVER Cloud Platform console. You can also utilize NAVER Cloud Platform's Cloud Insight to configure event and notification settings.

You can refer to the following guide:

• Monitoring
• Event

Manage management and administration permissions

You can create sub accounts in addition to the main user account and set various management and administration permissions for Cloud DB for MSSQL. You can design permissions by utilizing the System Managed and User Created policies in NAVER Cloud Platform's Sub Account.

You can refer to the following guide:

• Managing Cloud DB for MSSQL permissions

5. Set ACG

Set the Access Control Group (ACG) for an MSSQL server to allow the access of the application server to the created MSSQL server. You can refer to the following guide:

• ACG settings guide

6. Test MSSQL server connection

Use the MSSQL client and test to see if you can properly connect to the created MSSQL server. You can refer to the following guide:

• Getting started with Cloud DB for MSSQL