Cloud DB for MSSQL FAQ
    • PDF

    Cloud DB for MSSQL FAQ

    • PDF

    Article Summary

    Available in Classic and VPC

    This document contains answers to questions frequently asked on Cloud DB for MSSQL.
    If you cannot find an answer to your question in the following FAQs, you can search the user guide or submit an inquiry via Contact us.

    Cloud DB for MSSQL FAQ consists of the following topics.


    Service in general

    The following are general FAQs and answers regarding Cloud DB for MSSQL:

    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. 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.


    High availability

    The following are FAQs and answers regarding high availability of Cloud DB for MSSQL:

    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. Without FailOver and With FailOver are the available reboot modes. If you select Without FailOver, the settings made via SSMS are preserved. However, if you select With FailOver, the settings may be lost.


    Connected services

    The following are FAQs and answers regarding connected services of Cloud DB for MSSQL.

    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.


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.