Cloud DB for MSSQL overview

Available in Classic and VPC

You can easily build and automatically manage MSSQL databases with Cloud DB for MSSQL. It is a fully managed cloud database service that operates stably through NAVER's optimization settings, and it automatically recovers in case of failure occurrence.

Cloud DB for MSSQL features

Cloud DB for MSSQL provides the following features:

• Quick and easy installation: you can use the service right away after a few simple inputs and clicks.
• Optimization settings verified by NAVER services: MSSQL settings that have long been validated by different NAVER services are provided by default for fast and stable operation without the need for additional database configuration.
• Automatic data backup and creation of MSSQL server using the backed up data: data is automatically backed up once a day at the time designated by the customer, and data restoration is available by creating a new MSSQL server with the backed up data.
• Performance monitoring and notifications: various performance monitoring figures and graphs related to MSSQL and operating system are provided. When any failure or event arises, you are immediately notified via email or SMS.
• Easy query analysis: query level performance analysis conducted every minute is supported to enhance service performance and stability.
• Automatic failover support: if you use the high availability (HA) settings, then the server redundancy is configured with the principal server and mirror server. If the principal server fails, then it automatically fails over to the mirror server, enabling more stable operation of the server.

About Cloud DB for MSSQL user guide

Cloud DB for MSSQL provides services in the Korea Region. Check the following table of contents and their details for best use of Cloud DB for MSSQL.

• Cloud DB for MSSQL overview: introduction to Cloud DB for MSSQL, related useful resources, and FAQ
• Prerequisites for using Cloud DB for MSSQL: supported environments, server specifications, and pricing information for using Cloud DB for MSSQL
• Cloud DB for MSSQL scenarios: introduction to overall process for using Cloud DB for MSSQL
• VPC: information on getting started with, using, and managing permissions for Cloud DB for MSSQL in a VPC environment
  • Getting started with Cloud DB for MSSQL: how to subscribe to Cloud DB for MSSQL and manage it from the NAVER Cloud Platform console
  • Using Cloud DB for MSSQL: how to use MSSQL Server, Monitoring, Backup, Event, Config Group available in Cloud DB for MSSQL and how to access it externally
    • DB Server: introduction to creating, deleting, and managing MSSQL servers
    • Monitoring: introduction to checking server performance, operating system status, and query execution statistics for each MSSQL server through the dashboard
    • Backup: introduction to checking and restoring MSSQL server backup settings list
    • Event: introduction to checking events that occurred in MSSQL servers and creating rules
    • Config Group: how to create, edit, and delete Config Groups to apply to MSSQL servers
    • Accessing DB Server outside cloud: introduction to accessing DB servers externally
  • Managing Cloud DB for MSSQL permissions: how to manage Cloud DB for MSSQL permissions using Sub Accounts
• Classic: information on getting started with and using Cloud DB for MSSQL in a Classic environment
  • Getting started with Cloud DB for MSSQL: how to subscribe to Cloud DB for MSSQL and manage it from the NAVER Cloud Platform console
  • Using Cloud DB for MSSQL: how to use MSSQL Server, Monitoring, Backup, Event, Config Group available in Cloud DB for MSSQL and how to access it externally
    • DB Server: introduction to creating, deleting, and managing MSSQL servers
    • Monitoring: introduction to checking server performance, operating system status, and query execution statistics for each MSSQL server through the dashboard
    • Backup: introduction to checking and restoring MSSQL server backup settings list
    • Event: introduction to checking events that occurred in MSSQL servers and creating rules
    • Config Group: how to create, edit, and delete Config Groups to apply to MSSQL servers
    • Accessing DB Server outside cloud: introduction to accessing DB servers externally
• Cloud DB for MSSQL resource management: resource information and task history for each resource type in Cloud DB for MSSQL
• Cloud DB for MSSQL glossary: terms you must know when using Cloud DB for MSSQL and their descriptions:
• Cloud DB for MSSQL release notes: update history for Cloud DB for MSSQL guide

Cloud DB for MSSQL related resources

NAVER Cloud Platform provides a variety of related resources as well as the user guide to help customers better understand Cloud DB for MSSQL. If you are a developer or marketer in need of detailed information while you are considering adopting Cloud DB for MSSQL for your company or establishing data related policies, then please make good use of the resources below.

• Cloud DB for MSSQL (VPC) API Guide: how to use API for Cloud DB for MSSQL developers
• Cloud DB for MSSQL (VPC) CLI Guide: how to use CLI for Cloud DB for MSSQL developers
• Pricing plan introduction, characteristics, detailed features: summary of Cloud DB for MSSQL pricing system, characteristics, and detailed features
• Latest service news: the latest news on Cloud DB for MSSQL. Select category and service to see them
• FAQs: frequently asked questions from Cloud DB for MSSQL users
• Contact us: send direct inquiries in case of any unresolved questions that aren't answered by the user guide
• MSSQL documentation: guide on basic MSSQL concepts, how to use it, and tutorials
• SSMS documentation: guide on basic SSMS concepts, how to use it, and tutorials
• User guides for integrated services required for the use of Cloud DB for MSSQL
  • Server creation guide: how to create application servers that will communicate with MSSQL servers
  • VPC/Subnet user guide: how to create VPC/Subnet for MSSQL servers
  • ACG user guide: how to set ACG for MSSQL servers
  • Public IP user guide: how to configure public IP required for access environment settings in VPC
  • Port forwarding user guide: how to set port forwarding required for configuring access environment in a Classic environment
  • SSL VPN user guide: how to set SSL VPN required for access environment settings
  • Sub Account user guide: how to use Sub Account that helps managing Cloud DB for MSSQL and the administration permissions
  • Cloud Insight user guide: how to use Cloud Insight that helps with setting events that occur and notifications
  • Cloud Log Analytics user guide: how to use Cloud Log Analytics to help you collect and analyze MSSQL Server logs
  • Monitoring user guide: how to use Monitoring that helps the notification recipient settings for occurring events in the Classic environment
  • Object Storage user guide: how to use Object Storage to store backup files created by MSSQL Server

Check FAQs first.

You can get your questions answered quickly by referring to the answers in the FAQs before reading the user guide. If you haven't found the answer to your question in the following FAQs, then search the user guide for what you would like to know.

Q. What is the difference between VPC and Classic environments?
A. The Classic environment is a general cloud environment, while the VPC environment is a cloud environment that provides logically separated virtual private clouds (VPC).
Through VPCs, you can implement an environment similar to the existing data center network your company was using. Up to 3 VPCs can be created for each account. Each VPC provides a network address space with a maximum netmask of 0.0.255.255/16 (65,536 IPs).

Q. What are the tasks that need to be done in advance before creating MSSQL servers in Cloud DB for MSSQL?
A. You need to create an application server that will communicate with the MSSQL server.
However, a MSSQL server created from Cloud DB for MSSQL is currently only accessible within NAVER Cloud Platform, so the applications server must also be created inside NAVER Cloud Platform. For more information on how to create it, see Cloud DB for MSSQL scenarios and Getting started with Cloud DB for MSSQL.

Q. How do I access the MSSQL servers I created?
A. You can access by using a private domain in the NAVER Cloud Platform server, or access from outside of the cloud by using an SSL VPN or public domain.
For more information on access methods using a private domain from a NAVER Cloud Platform server, see Getting started with Cloud DB for MSSQL. For more information on access methods from outside of the cloud, see Access using SSL VPN and Access using public domain respectively.

Q. How can I manage databases by directly accessing an MSSQL server rather than accessing through the application server?
A. You can use SSMS to directly access and manage MSSQL servers.
For more information on how to use each utility, see Accessing DB from outside cloud.

Q. Are there tasks I should avoid using SSMS?
A. Do not make any changes (rename, password change, etc.) to USER_ID for management which you create at the time of server creation.
If you create a user or change password on SSMS, it may not be replicated in a mirror server.
Also, if you create a database directly on SSMS UI, you should change the recovery model option to "Full" to enable the replication to the mirror.

Q. When using the high availability settings, what is the difference between a principal server and a mirror server?
A. While an MSSQL server is being operated normally, the mirror server does not play any role and simply replicates the principal server's data as it is. If the principal server fails and can no longer be operated normally, then it automatically performs a failover where the mirror server takes over the role of the principal server.

Q. If I restart the principal server, does it automatically perform a failover?
A. You can select a reboot mode when restarting the server. There are two reboot modes: without failover, which guarantees your SSMS configuration to be maintained but may incur a few minutes of service downtime or more, and With failover, which has a shorter downtime of less than 30 seconds, but you have to take the risk of losing your SSMS configuration.

Q. Regarding the performance or operating system of MSSQL servers, is there a feature that enables the configuration of thresholds and notifies the admin of the events that occurred when they are exceeded?
A. By default, Cloud DB for MSSQL provides monitoring service and event collection service for the performance and operating system of the server.
In addition, you can directly set thresholds and notifications via email or SMS for occurring events by integrating with Cloud Insight. For more information on usage methods, see Monitoring and Event.

Q. Can I use linked servers in Cloud DB for MSSQL?
A. Linked servers are unavailable in Cloud DB for MSSQL.
Note that you should configure it yourself using general installation type MSSQL to use linked servers with MSSQL.