DB Server

Available in Classic

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 Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
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.
     • : It changes the service name when clicked.
   • DB role: MSSQL server's role
     • 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: MSSQL server's name
   • MSSQL server type: MSSQL server's server type and available memory
   • Monitoring: Go to the Monitoring page.
   • DB status: Go to the MSSQL server's View details page.
   • DB access port: port number being used by the MSSQL server
   • Zone: It indicates the zone that the MSSQL server belongs to.
   • Private domain: information of the private domain
   • Public domain: the public domain information accessible from the outside
     • Displayed only when it is set through the public domain management feature in 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 capacity in use of the data storage in use
   • Status: MSSQL server's status
     • 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 has 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 created with the information entered by the user is being deleted
     • Stopping: status in which the MSSQL server created with the information entered by the user is being stopped
     • Restarting: status in which the MSSQL server created with the information entered by the user is being restarted
   • Creation date and time: date when the MSSQL server was created, the initial point when the server entered the Creating status
   • Start date and time: date when the MSSQL server started running, the initial point when the server entered the Running status
   • ACG: name and ID of the ACG being used in the MSSQL server
     • : Directs to the Server > ACG page when clicked.
     • [View rules] button: It displays detailed rules applied when clicked.
   • Database config: the config applied to the MSSQL server
     • : Changes can be made to the DB config group when clicked.
   • DB engine version: version information of the MSSQL installed on the server
   • DB license: license information of the MSSQL installed on the server
   • High availability: It displays whether the high availability feature is being used with Y or N.
     • : You can change whether to use high availability by clicking it.
   • Backup retention period (backup time): when using the backup feature, displays the information of the configured backup file retention period and backup execution cycle
     • : Sets backup feature use status, file retention period, and execution cycle when clicked.
   • Collation: character set of the MSSQL installed on the server
   • Scheduled reboot time: scheduled time for restarting the server

Create MSSQL server

The following describes how to create an MSSQL server.

1. From the Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
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 engine version: version information of MSSQL 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 lower 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 items related to zone and MSSQL server, which are needed for the creation of the MSSQL server.
   • Zone: Select a zone to create the MSSQL server in.
   • 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.
4. Set Support high availability for the availability of the server to be created.
   • When selected, redundancy is configured with two MSSQL servers: principal server and mirror server.
   • Performs a failover for automatic recovery in case of failure.
   • When selected, set backup file retention 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.
5. Check the applicable pricing plan information when using Cloud DB for MSSQL.
   • Pricing plan: 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 rest of the items required for the creation of the MSSQL server.
   • DB service name: Enter the group name that classifies the MSSQL server to be created by its role. <Example> mssql-service
     • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
     • A duplicated name can't be used.
   • Set ACG: Access Control Group (ACG) is created automatically.
     • The detailed settings for the ACG is 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.
     • Enter between 4 and 16 characters using English letters, numbers, and special characters "_".
     • 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.
     • Enter 8 to 20 characters containing at least one English letter, number, and special character.
     • The special characters ` & ₩ " ' / or spaces can't be used.
   • DB access port: Enter the TCP port number to be 1433, or a number from 10000 to 20000 to allow access to the MSSQL server to be created.
     • Default value: 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.
   • DB log collection: Check if error logs are collected and the viewer feature is provided.
     • Cloud Log Analytics linkage
2. Set whether to use the backup for the server to be created.
   • Backup settings: Set whether to use backup, backup file retention period, and backup time.
     • Backup file retention period: Click and select the period to store the backup file to 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.
     • When selected, additional fees will be incurred according to the storage capacity used.
       • Automatic: Backup is automatically started every day.
       • User-defined: The backup is started every day within 15 minutes from the time specified by the user.
3. Click the [Next] button.
4. When the Request Cloud Log Analytics subscription, check the content, and then click the [OK] button.
   • If you need to request subscription to Cloud Log Analytics, click the [Request subscription to Cloud Log Analytics].
   • Refer to Cloud Log Analytics Guide for detailed description of Cloud Log Analytics.

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 in 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 has 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 select a rebooting schedule reserved and restart it.

1. From the Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
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 you 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 [Schedule rebooting] after setting the search period and filtering conditions.
   • Rebooting can be scheduled to be the time when 3 minutes have passed from the point of setting up.
   • If you want to restart the server immediately without scheduling it, click the [Reboot now] button.
6. Check the status of the MSSQL server from the MSSQL server list in the DB server page.
   • Restarting: status in which the MSSQL server is being restarted
   • Running: status in which the server has been restarted, and access to the MSSQL server can be made from the application server

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 Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
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 in 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 Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
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 Classic environment of the NAVER Cloud Platform console, click the Services > Database > Cloud DB for MSSQL menus, in that order.
2. Click the DB server menu.
3. Click the MSSQL server you want to manage, and then click the [Manage DB] button.
4. Click and select the management item you need.
   
   • View DB server details
   • Change DB specifications
   • Manage DB config
   • Manage DB user
   • Manage database
   • Manage public domain
   • Manage backup settings
   • Add slave
   • Adjust time available for reading

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.

Change MSSQL server 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 will be incurred when 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 to.
   
3. Click the [OK] button.
4. Check the status of the MSSQL server with the specifications modified, from the MSSQL server list in the DB server page.
   • Configuring: status in which the MSSQL server is being configured with the information entered by the user
   • Running: status in which the configuration of the MSSQL server has been completed with the information entered by user, and access to the MSSQL server from the application servers 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 the DB service upon change. The application is available after creating a config group. For detailed methods for creating, editing, and deleting config groups, please refer to Config group.

The following describes how to change it.

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 in 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 in the DB server page.
   • Restarting: status in which the MSSQL server is being restarted
   • Running: status in which the server has been restarted, and access to the MSSQL server can be made from the application server

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 one 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 name of the database to add in Database name, and click the [Add database] button.
     • Enter between 1 and 20 characters using English letters, numbers, and special characters "_".
     • It must start with an English letter.
   • Delete: Click the [Delete] button on the row of the database created.
3. Click the [Save] button.

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 in the DB server page.
   • Configuring: status in which the MSSQL server is being configured with the information entered by the user
   • Running: status in which the configuration of the MSSQL server has been completed with the information entered by user, and access to the MSSQL server from the application servers is available

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.

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 for 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.
3. Click the [OK] button.
4. Check the status of the slave server that was created from the MSSQL server list in 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 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.