DB Server

Available in VPC

In DB Server, you can create or delete MSSQL servers, as well as check the list of MSSQL servers in operation. In addition, you can change the specifications for the MSSQL servers in operation, or manage admin (user) accounts.

DB server page

The basics of using MSSQL server are as follows:

View MSSQL server list

You can check the information of each server from the list of MSSQL servers that have been created and are in operation. The following describes how to view the information.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. If the list of created MSSQL servers appears, then check the summary information or click an MSSQL server to check the details.
   
   • DB service name: service name of MSSQL, a group that classifies MSSQL servers by role. It generally refers to a server group that consists of one principal server, one mirror server, and multiple slave servers. MSSQL servers with the same data are referred to as one service.
     • : click to change the service name
   • DB Role: roles of the MSSQL Server
     • Principal: the master server when the high availability support is selected
     • Mirror Master: the standby server when the high availability support is selected. If the master server fails, then it automatically performs the role of the master.
     • Standalone: the single server when the high availability support is not selected
   • MSSQL Server name: name of the MSSQL Server
   • MSSQL Server type: type of the MSSQL server and its available memory
   • Monitoring: directs to the monitoring page
   • DB status: directs to the View MSSQL Server details page
   • DB access Port: port number being used by the MSSQL server
   • Private domain: information of the private domain
   • Public domain: information of the public domain which allows external access
     • This is displayed only when public domain is enabled through public domain management in the Manage DB menu
   • Data storage: size of the data storage in use (available capacity)
   • Data storage type: type of the data storage in use
   • Data storage capacity: available capacity and used capacity of the data storage in use
   • Status: status of the MSSQL server
     • Creating: status in which the MSSQL server is being created with the information entered by the user
     • Configuring: status in which the MSSQL server is being configured after being created with the information entered by the user
     • Running: status in which the creation and configuration of the MSSQL server have been completed with the information entered by user, and access to MSSQL from the application server is available
     • Deleting: status in which the MSSQL server is being deleted with the information entered by the user
     • Stopping: status in which the MSSQL server is being stopped with the information entered by the user
     • Restarting: status in which the MSSQL server is being restarted with the information entered by the user
   • Creation date: date when the MSSQL server was created, the initial point when the server entered Creating status
   • Running date: date when the MSSQL server started running, the initial point when the server entered Running status
   • ACG: ACG name and ID used in the MSSQL server
     • : click to move to Server > ACG
     • [View rules] button: click to display the detailed rules applied
   • Database Config: Config applied to the MSSQL server
     • : set the DB Config Group when clicked
   • DB engine version: version information of the MSSQL installed on the server
   • VPC: VPC name used in the MSSQL server
   • Multi Zone: displays whether the Multi Zone is configured with Y or N
   • Subnet: name of the subnet being used by the MSSQL server
   • High availability: whether high availability is enabled (Y or N)
     • : set whether to use high availability when clicked
   • Backup storage period (backup time): the configured backup file storage period and backup cycle, if the backup function is enabled
     • : click to enable or disable backup or set the file retention period and backup cycle
   • Collation: MSSQL character sets installed in the server

Create MSSQL server

The following describes how to create an MSSQL server.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. Click the [Create DB server] button.
   
4. When the subscription request page appears, proceed with the following steps in order.
   • 1. Set server
   • 2. Set DB
   • 3. Final confirmation

1. Set server

The following describes how to create a server to install MSSQL by entering the settings.

1. When the Set server page appears, check the type of DBMS you want to install to the server from DBMS type.
   
2. Check the version and character set information of the MSSQL to be installed.
   • DB Edition: currently, DB Edition provides MSSQL Standard Edition and Enterprise Edition.
   • DB engine version: information of the MSSQL version that can be created in NAVER Cloud Platform
   • DB character set (collation): character set information of MSSQL that can be created in NAVER Cloud Platform
     • Korean_Wansung_CI_AS: Korean letter complete type, no distinction between upper and lowercase characters or accents
     • SQL_Latin1_General_CP1_CI_AS: English version's default value, no distinction between upper and lower characters or accents
3. Set additional options for the availability of the server to be created.
   • Support high availability: click to select whether to use the failover feature for automatic recovery in case of failure
     • When selected, redundancy is configured with two MSSQL servers: principal server and mirror server
     • When selected, set backup file storage period and backup time (default: one day, automatic)
     • When selected, disabling the storage of backup files is not possible
     • When selected, additional fees will be incurred
     • A mirror server is not accessible by the user
   • Multi Zone: to secure advanced high availability, click to select whether to create a principal server and mirror server separately in 2 different zones (1 in each zone)
4. Set items related to VPC and MSSQL server, which are needed for the creation of the MSSQL server.
   • VPC: select the VPC to be used for the creation of the server and MSSQL
     • [Refresh] button: click to refresh the list of created VPC list
     • [Create VPC] button: click if you don't have any VPCs that have been created and need to create one
   • Subnet: select a private subnet to be used when accessing VPC
     • [Refresh] button: click to refresh the list of created subnet list
     • [Create subnet] button: click if you don't have any subnets that have been created, but you need to create one
   • DB Server type: select the MSSQL server type to be created and available memory according to the server type
   • Data storage type: click to select the storage type for saving DB data, between SSD and HDD
     • The settings can't be changed after the creation of the MSSQL server.
   • Data storage capacity: check the storage capacity for saving DB data
     • 100 GB is assigned upon initial creation of an MSSQL server.
     • The capacity is automatically added in 10 GB units and charged as data increases
     • Up to 2000 GB is supported.
5. Check the applicable pricing plan information when using Cloud DB for MSSQL.
   • Pricing plan: an hourly pricing plan, which is billed based on the hours used, is applied by default, and it is changed according to the server specifications and storage capacity
   • Click Pricing information for more information
6. Set the rest of the items required for the creation of the MSSQL server.
   • DB service name: enter a group name that classifies MSSQL servers that will be created by role
     • The name must be 3-15 characters long and can only include Korean letters, English letters, numbers, and the hyphen (-)
     • A duplicated name can't be used
   • Set ACG: access control group (ACG) is created automatically
     • The detailed settings for the ACG are available from Server > ACG in the console
7. Click the [Next] button.

2. Set DB

The following describes how to set the information for the MSSQL to be installed.

1. When the Set DB page appears, set items needed for the creation of the MSSQL server.
   
   • USER_ID: enter the account ID of the MSSQL server admin
     • The ID must be 4-16 characters using English letters, numbers, and the underscore (_)
     • It must start with an English letter
     • Predefined reserved words can't be used
   • USER password: enter the account password of the MSSQL server admin
     • The password must be 8-20 characters long and can only include English letters, numbers, and special characters, with at least one of each
     • The special characters ` & ₩ " ' / or spaces can't be used
   • DB access port: enter 1433 or between 10000 to 20000 as a TCP port number to allow access to the MSSQL server that will be created
     • Default: 1433
     • The port number can't be changed after it is specified
   • DB config settings: check the optimized basic settings provided by NAVER
     • A Config Group created in advance can be applied when you create a server
   • Collect DB log: check the provision of log collection and viewer features for error logs
     • Cloud Log Analytics integration
2. Set whether to use the backup for the server to be created.
   • Backup settings: set whether to use the backup, backup file retention period, and backup time
     • Backup file retention period: click and select the period to store the backup file in a separate backup storage
       • For point-in-time recovery, the backup file is stored for the maximum retention period possible + 24 hours.
       • Daily full backup and regular transaction backup are performed
     • Backup time: select the full backup execution time between automatic and user-defined
     • If you select this, additional fees will be incurred according to the storage capacity used
       • Automatic: backup is automatically started every day
       • User-defined: backup is started every day within 15 minutes from the time selected by the user
3. Click the [Next] button.
4. When Subscribe to Cloud Log Analytics Service appears, check the content, and then click the [OK] button.
   • If you need to request a subscription to Cloud Log Analytics, click the [Request subscription to Cloud Log Analytics]
   • For more information on Cloud Log Analytics, see Cloud Log Analytics user guide

3. Final confirmation

1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
   
   • Click the [Previous] button to edit the settings
2. Click the [Create] button.
3. Check the status of the MSSQL server that was created from the server list on the DB server page.
   • Creating: status in which the MSSQL server is being created with the information entered by the user
   • Configuring: status in which the MSSQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MSSQL server have been completed with the information entered by user, and access to MSSQL from the application server is available

Restart MSSQL server

You can easily and conveniently restart MSSQL servers. You can't access servers while they're being restarted. The following describes how to restart.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. Click the MSSQL server you want to restart, and then click the [Restart DB server] button.
4. When the OS reboot pop-up window appears, select how to reboot the server.
   • Without failover: the user's SSMS configuration content is guaranteed, but the service downtime may take several minutes.
   • With failover: the service downtime doesn't exceed 30 seconds, but the user's SSMS configuration content may be lost.
5. Click the [Reboot] button.
6. Check the status of the MSSQL server from the MSSQL server list on the DB server page.
   • Restarting: status in which the MSSQL server is being restarted
   • Running: status in which access to the MSSQL server from the application server is available due to the server being rebooted up

Delete MSSQL server

You can delete an MSSQL server that has been created and is in operation.

If you're using high availability, then both the principal server and mirror server will be deleted. If you have slave servers, then you need to first delete all slave servers from the DB service before deleting the principal server. If you're using the backup feature, then the backup files are also deleted.

The following describes how to delete MSSQL servers.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. Click the MSSQL server you want to delete, and then click the [Delete DB server] button.
4. When the Delete DB server pop-up window appears, enter the name of the MSSQL server to delete, and then click the [OK] button.
5. Check the status of the MSSQL server from the MSSQL server list on the DB server page.
   • Deleting: status in which the MSSQL server is being deleted

MSSQL server monitoring

NAVER Cloud Platform's Cloud DB for MSSQL provides a monitoring service through the dashboards on each server. This allows users to intuitively check servers in operation and data status and efficiently manage them.

The following describes how to go to the monitoring page of the MSSQL server that has been created and is in operation.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. Click the MSSQL server you want to monitor, and then click the [Monitoring] button.
4. Click and select the dashboard you want to monitor.
   

Manage MSSQL server

While operating the created MSSQL server, situations where you need to change the options related to the server or DB configured upon creation may occur. Cloud DB for MSSQL supports change or upgrade of some specifications through a few simple clicks, even for MSSQL servers that have already been created.

The following describes how to manage the MSSQL server that has been created and is in operation.

1. From the VPC environment of NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click DB server.
3. Click the MSSQL server you want to manage, and then click the [Manage DB] button.
4. Click and select the item you want to manage.
   
   • View DB server details
   • Add slave
   • Adjust time available for reading
   • Change high availability settings
   • Change DB specifications
   • Manage DB config
   • Manage public domain
   • Manage DB user
   • Manage database
   • Manage Backup settings
   • MSSQL Engine Upgrade
   • Manage Audit settings
   • Change DB service name

View MSSQL server details

You can check the details related to the server to see if the selected MSSQL server is running properly. The details are as follows:

Add slave server

You can add readable slave servers to the MSSQL servers using the high availability settings. Private domains are assigned by default to the slave servers, and public domains can also be assigned separately. Up to 5 slave servers can be added for one master server.

The settings of a principal server are applied identically to its slave servers.

• MSSQL server type
• Data storage type
• Data storage capacity
• DB config settings

The same fees apply to the slave servers as the principal server, and the fees are charged based on the hours used. The following describes how to add slave servers.

1. When the Add slave DB server pop-up window appears, check the information for the principal server and the slave server.
   
2. Enter the unique 3-digit number (001-999) for the domain you'd like to use, and click the [Check for duplicate domains] button.
   • Select a subnet to create the slave server in if you're using the multi-zone configuration.
3. Click the [OK] button.
4. Check the status of the slave server that was created from the MSSQL server list on the DB server page.
   • Creating: status in which the slave server is being created with the information entered by the user
   • Configuring: status in which the slave server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the slave server has been completed with the information entered by user, and the access to the slave server from the application server is available

Adjust time available for reading

Slave servers work with the log shipping method, and they are not available to be used for service directly. You can set it up to be available for reading during a certain time every day to be used for batch jobs, etc. DB restoration won't be carried out during the set time so that it is available for reading. Up to 20-time ranges can be selected as the time available for reading.

You can configure it as follows:

1. When the Adjust time available for reading pop-up window appears, check the times set as available for reading.
2. Select the time range you want available for reading, and then click the [OK] button.
   

Change high availability settings

You can change the selected MSSQL server into a standalone or high-availability configuration. The following describes how to change.

1. When the Change high availability settings pop-up window appears, check the basic server information.
   
2. If the existing high availability setting is Y, it may be set to standalone. If the existing high availability setting is N, it may be set to high availability.
   • If changing to a high availability configuration, click and select whether to use a multi-zone.
     When selected, a primary DB and a secondary DB are created in different zones to provide higher availability.
3. Click the [Yes] button.
4. Check the status of the MSSQL server from the MSSQL server list on the DB server page.
   • Configuring: status in which the MSSQL server is being configured after being created with the information entered by the user
   • Running: status in which the creation and configuration of the MSSQL server has been completed with the information entered by user, and the access to MSSQL from the application server is available

Change DB specifications

You can change the server specifications for the MSSQL server you created. When changing the server specifications, the specifications for the master, mirror, and slave servers are also all changed. Additional fees are incurred for upgrading specifications.

The following describes how to change the specifications.

1. When the Change DB server specifications pop-up window appears, check the current server specifications.
2. Click and select the server specifications you want to change.
   
3. Click the [OK] button.
4. Check the status of the MSSQL server with the specifications modified from the MSSQL server list on the DB server page.
   • Configuring: status in which the MSSQL server is being configured after being with the information entered by the user
   • Running: status in which the creation and configuration of the MSSQL server has been completed with the information entered by user, and the access to MSSQL server from the application server is available

Manage DB config

You can change Config Groups to apply to MSSQL servers you created. The changed Config Group is applied to all servers within the same service group, and some Config variables are applied after an automatic restart of DB Service upon change. The application is available after creating a Config Group. For more information about methods for creating, editing, and deleting Config Groups, see Config Group.

The following describes how to change.

1. When the Change DB Config Group window appears, check the Config Group currently applied.
2. Click and select the Config Group to change to.
   
3. Click the [Change] button.
4. Click the MSSQL server with the changed Config Group from the MSSQL server list on the DB Server page.
5. Click the [Restart required] button under Database Config.
6. Check the status of the MSSQL server from the MSSQL server list on the DB server page.
   • Restarting: status in which the MSSQL server is being restarted
   • Running: status in which access to the MSSQL server from the application server is available due to the server being rebooted up

Manage public domain

You can request a public domain to allow access to MSSQL server from outside of NAVER Cloud, or remove the configured public domain. If you've set up a public domain, you will be charged for the amount of network usage for the data used for external communication. If you remove the public domain, access to the DB server is only available within NAVER Cloud Platform.

The following shows how to set up or remove a public domain.

1. When the Request public domain pop-up window appears, check the DB server's name.
   • If you're to remove the public domain assigned, the Remove public domain pop-up window will appear. Check the DB server name and public domain.
     
2. Click the [Yes] button.
3. Check the status of the MSSQL for which you've set the DB failover, from the MSSQL server list on the DB server page.
   • Configuring: status in which the MSSQL server is being configured after being with the information entered by the user
   • Running: status in which the creation and configuration of the MSSQL server has been completed with the information entered by user, and the access to MSSQL server from the application server is available

Manage DB user

You can change the password of the admin DB account for the MSSQL server created.

The following describes how to change the password of an admin account.

1. When the Manage DB user pop-up window appears, check the DB admin account.
2. Enter the new password.

• Enter between 8 and 20 characters containing at least 1 English letter, number, and special character.
• Special characters ` & ₩ " ' / and spaces can't be used.
  

3. Click the [Save] button.

Manage database

You can add DBs to the selected MSSQL server or delete them. Up to 3 DBs can be added or deleted at one time.

The following describes how to add or delete databases.

1. When the Manage Database pop-up window appears, check the database information.
2. Add or delete databases.
   
   • Add: enter the database name to add to Database Name and then click the [Add database] button.
     • The ID must be 1-20 characters using English letters, numbers, and the underscore (_)
     • It must start with an English letter
   • Delete: click the [Delete] button for the created database row.
3. Click the [Save] button.

Manage Backup settings

You can set the backup file retention period and backup time for the selected MSSQL server. The backup files can be kept for a minimum of 1 day and a maximum of 30 days. The backup will be performed within 15 minutes of the time selected.

The following describes how to set up backup retention period and backup time.

1. When the Backup retention period (backup time) pop-up window appears, check the backup settings information.
2. Set the backup file retention period and backup time.
   
3. Click the [Save] button.

MSSQL Engine Upgrade

You can upgrade the minor version of MSSQL Engine. The version upgrade is applied to the entire DB service, and the upgrade is performed one server at a time in the following order: slaves -> mirror -> principal. The server access is unavailable during the upgrade.

1. Click Manage DB > MSSQL Engine Upgrade.
2. Select the version to upgrade and click the [Yes] button.

Change DB service name

You can change the service name.

Manage Audit settings

• You can leave a record of the DB server's logins and the creation, modification, and deletion of objects in the database (DDL).
• If you select Enable audit logs, it is set throughout the DB cluster.
• Audit information is generated using SQL Server Extended Events.
• You can monitor in real time on the audit Logs tab of the Monitoring menu and download it from the Download Log menu.

1. Click Manage DB > View DB service details.
2. In Manage Audit settings, change Audit to [Enable] and specify the desired config value.
3. Click the [Save] button.
4. If there is a config value to be edited, change only the config value in the active state and click the [Save] button.
5. When deleting a plugin, change the Audit value to [Disabled] and click the [Save] button.

• Audit Config variable list

• Audit log management and backup method

  • The audit log file provided by Cloud DB for MSSQL is rolled over by the MaxFileSize config value and MaxRolloverFiles config value when setting the audit.
  • Users can note the last edited date of the auditlog file and download it to Object Storage using the Download Log > Audit Log menu.

• List of audit log fields

Download Log

You can download the Error log, Default Trace File, Agent Log, and Audit Log files.