DB Server

Prev Next

Available in VPC

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

DB Server interface

The basic description of using MSSQL Server is as follows:

clouddbformssql-dbserver_screen_vpc_ko

Component Description
① Menu name Current menu name and number of MSSQL Servers in operation.
② Basic features Create an MSSQL Server, check details for Cloud DB for MSSQL, and reload the DB Server screen.
③ Post-creation features Restart, delete, monitor, and manage MSSQL Servers in operation.
④ MSSQL Server list Check the list of MSSQL Servers in operation and their information.
⑤ Search Search the server you want by the service name from the MSSQL Server list.

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. To view the information:

Note

You can view the list only when there are 1 or more servers in operation. If you do not have any servers created and operating, no list appears on the DB Server screen.

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. If the list of created MSSQL Servers appears, then check the summary or click an MSSQL Server to check the details.
    clouddbformssql-dbserver_details_vpc_ko
    • DB service name: Service name of MSSQL, a group that classifies MSSQL Server by role. This generally refers to a server group that consists of 1 Principal Server, 1 Mirror Server, or multiple Slave Servers. MSSQL Servers with the same data are referred to as the same service.
      • clouddbforpg_ico-02: Click to change the service name.
    • DB Role: Roles of the MSSQL Server.
      • Principal: Master Server when the Support high availability is selected.
      • Mirror Master: Standby Server when the Support high availability is selected. If Master Server fails, then it automatically performs the role of Master.
      • Stand Alone: The single Server when the Support high availability is not selected.
    • MSSQL Server name: Name of the MSSQL Server.
    • MSSQL Server type: Type of the MSSQL Server and its available memory.
    • Monitoring: Go to the monitoring screen.
    • DB Status: Go to the View MSSQL Server details screen.
    • 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 that allows external access.
      • This is displayed only when Public domain is enabled through Public domain management features in the Manage DB menu.
    • Data storage: Size of the data storage in use (available capacity).
    • Data storage type: Type of 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 created and configured 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 the user, enabling the application server access to the MSSQL.
      • 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 the 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.
      • clouddbforredis-start_ico-01: Click to move to Server > ACG.
      • [View rules]: Click to view the detailed rules applied.
    • Database Config: Config applied to the MSSQL Server.
      • clouddbforpg_ico-02: 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 Subnet being used by the MSSQL Server.
    • High availability: Whether the high availability feature is enabled (Y or N).
      • clouddbforpg_ico-02: Set whether to use high availability configuration when clicked.
    • Backup storage period (backup time): The configured backup file storage period and backup cycle, if the backup feature is enabled.
      • clouddbforpg_ico-02: Click to enable or disable the backup feature or set the file retention period and backup cycle.
    • Collation: MSSQL character sets installed in Server.
Note
  • Principal Server is the server that is important for performing database-related tasks.
  • Mirror Server does not do anything while MSSQL Server is operating normally and replicates the data on Principal Server 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.
Caution

If you clear the backup, all existing backup files are deleted.

Create MSSQL Server

To create an MSSQL server:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. Click [Create DB Server].
    clouddbformssql-dbserver_create_vpc_ko
  4. When the subscription request screen appears, proceed with the following steps in order:
Note

Click [Subscribe] in Services > Database > Cloud DB for MSSQL on the NAVER Cloud Platform portal to directly go to the screen in step 3.

1. Set server

To create a Server to install MSSQL by entering the settings:

  1. When the Set server screen appears, check the type of DBMS you want to install on the server from DBMS type.
    clouddbformssql-dbserver_create2_vpc_ko

  2. Check the settings required when creating MSSQL servers.

    • Server generation: Information categorized based on the hypervisor type of MSSQL servers.
      • G2: XEN-based.
      • G3: KVM-based.
    • DB Edition: Currently, DB Edition provides MSSQL Standard Edition and Enterprise Edition.
    • DB engine version: Information on 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, configure redundancy with 2 MSSQL Servers, Principal Server and Mirror Server.
      • When selected, set backup file retention period and backup time (default: 1 day, automatic).
      • When selected, disabling the storage of backup files is not possible.
      • When selected, additional fees will be incurred.
      • The user does not have access to Mirror Server.
    • 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]: Click to refresh the list of created VPCs.
      • [Create VPC]: Click if you haven't created any VPC and need to create one.
    • Subnet: Select a Private Subnet to be used when accessing VPC.
      • [Refresh]: Click to refresh the list of created Subnet list.
      • [Create Subnet]: Click if you haven't created any Subnet and need to create one.
    • DB Server type: Select the MSSQL Server type to be created and available memory depending on the server type.
    • Data storage type: Storage type for saving DB data.
      • The settings can't be changed after the creation of the MSSQL Server.
      • When you select G2 as the server generation, select SSD or HDD.
      • When you select G3 as the server generation, automatically set to SSD.
    • Data storage capacity: View 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 2,000 GB for G2 and up to 4,000 GB for G3.

  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 depending on the server specifications and storage capacity.
    • For more information, click Pricing information.

  6. Set the rest of the items required for the creation of MSSQL Server.

    • DB Service name: Enter a Group name that classifies MSSQL Server that will be created by role.
      • Enter between 3 and 15 characters using Korean letters, English letters, numbers, and hyphens (-).
      • Duplicate names are not allowed.
    • 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 [Next].

2. Set DB

To set the information for the MSSQL to be installed:

  1. When the Set DB screen appears, set items needed for the creation of the MSSQL Server.
    clouddbformssql-dbserver_create3_vpc_ko
    • USER_ID: Enter the account ID of the MSSQL Server admin.
      • Enter between 4 and 16 characters using English letters, numbers, and the underscore (_) special character.
      • The first character must be an English letter.
      • You cannot use predefined reserved words.
    • USER password: Enter the account password of the MSSQL Server admin.
      • Enter 8 to 20 characters using at least 1 English letter, number, and special character.
      • 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: View 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 the log collection and viewer feature for error logs.
      • Cloud Log Analytics integrations.
  2. Set whether to use backup for the server.
    • 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.
        • 1-time full backup for 1 day 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 depending on the storage capacity used.
        • Automatic: Backup is automatically started every day.
        • User-defined: Backup is started every day within +15 minutes from the time you selected.
  3. Click [Next].
  4. When Subscribe to Cloud Log Analytics service appears, check the content, and then click [OK].
    • If you need to subscribe to Cloud Log Analytics, click [Subscribe to Cloud Log Analytics].
    • For more information about Cloud Log Analytics, see Cloud Log Analytics user guide.

3. Final confirmation

  1. When the final confirmation screen appears, view the configured server information, DB information, and Backup information.
    clouddbformssql-dbserver_create4_vpc_ko
    • Click [Previous] to edit the settings.
  2. Click [Create].
  3. Check the status of the MSSQL Server that was created from the server list on the DB Server screen.
    • 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 created and configured 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 the user, enabling the application server access to the MSSQL.
Note

To view the latest status from step 3, click [Refresh].

Caution

It may take several minutes or longer until it enters the Running status, and is available for actual use, after going through Creating and Configuring statuses.

Restart MSSQL Server

You can easily and conveniently restart MSSQL Server. You can't access servers while they're being restarted. To restart:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. Click the MSSQL Server you want to restart, and then click [Restart].
  4. When the OS Reboot popup window appears, select how to reboot the server.
    • Without FailOver: The user's SSMS configuration content is guaranteed, but the service down time may take several minutes.
    • With FailOver: The service down time doesn't exceed 30 seconds, but the user's SSMS configuration content may be lost.
  5. Click [Reboot].
  6. Check the status of the MSSQL Server from the MSSQL Server list on the DB Server screen.
    • 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.
Caution

The process may take a few minutes to progress through Restarting status and reach Running status where actual usage becomes available.

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.

To delete MSSQL Server:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. Click the MSSQL Server you want to delete, and then click [Delete DB Server].
  4. When the Delete DB Server popup window appears, enter the name of the MSSQL Server to delete, and then click [Yes].
  5. Check the status of the MSSQL Server from the MSSQL Server list on the DB Server screen.
    • Deleting: Status in which the MSSQL Server is being deleted.
Caution

The actual deletion from the list after going through the Deleting status may take several minutes.

Monitor MSSQL Server

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

Note

For more information on Monitoring, see Monitoring.

To go to the monitoring screen of the MSSQL Server that has been created and is in operation:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. Click the MSSQL Server you want to monitor, and then click [Monitoring].
  4. Click and select the dashboard you want to monitor.
    clouddbformssql_dbserver_monitoring

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 Server that has already been created.

Note

By default, managing a MSSQL Server is available when the server status is running.

To manage the MSSQL Server that has been created and is in operation:

  1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for MSSQL.
  2. Click the DB Server menu.
  3. Click the MSSQL Server you want to manage, and then click [Manage DB].
  4. Click and select the item you want to manage.
    clouddbformssql_dbserver_task

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:

View details tab Description Item
Manage DB Config Change settings for the selected MSSQL Server. For more information, see Manage DB Config.
Manage Database Add DBs to the selected MSSQL Server or delete them. For more information, see Manage Database.
Manage DB user You can change the password of the admin DB account for the MSSQL Server selected. For more information, see Manage DB user.
Manage Backup settings Set the backup file retention period and backup time for the selected MSSQL Server. For more information, see Manage Backup settings.
Change DB specifications Change specifications for the selected MSSQL Server. For more information, see Change DB specifications.
Manage Audit settings Audit settings for the selected MSSQL Server. For more information, see Manage Audit settings.
Download Log Download log for the selected MSSQL Server. For more information, see Download Log.
Note
  • Since VPC-based Cloud DB for MSSQL allows direct session search and kills from the SSMS tool, it doesn't provide the viewing Process List and Lock features.

Add Slave Server

You can add a readable Slave Server to the MSSQL Server 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 1 Master Server.

Caution

A Slave DB Server is configured with log Shipping, and is not available for reading 24 hours a day. It can't be read while Transaction log backup is being carried out, rendering it unavailable for a general service. It is suitable for tasks such as regular read batch and data checking by setting up a time when reading is available.

Note
  • You can't add Slave Server to the Stand Alone Server.
  • If data replication through log forwarding fails, the read only server is reconfigured on the same server. While doing so, you may not be able to access the server briefly.

The settings of Principal Server are applied identically to its Slave Server.

  • MSSQL Server type
  • Data storage type
  • Data storage capacity
  • DB Config settings

The same fees apply to Slave Server as Principal Server, and the fees are charged based on the hours used. To add Slave Server:

  1. When the Add Slave DB Server popup window appears, check the information for the Principal Server and the Slave Server.
    clouddbformssql-dbserver_addSlave_vpc_ko
  2. Enter the unique 3-digit number (001-999) for the domain you'd like to use, and click [Check for duplicate domains].
    • For Multi Zone configurations, select the subnet where you want to create the Slave Server.
  3. Click [OK].
  4. Check the status of the Slave Server that was created from the MSSQL Server list on the DB Server screen.
    • Creating: Status in which the Slave Server is being created with the information you entered.
    • Configuring: Status in which the Slave Server is being created and configured with the information you entered.
    • Running: Status in which the creation and configuration of the Slave Server have been completed with the information you entered, enabling the application server access to the Slave Server.

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, and so on. DB restore 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.

To set:

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

Change high availability settings

You can change the selected MSSQL server to a standalone or high availability configuration. To change:

  1. When the Change high availability settings popup window appears, view the basic server information.
    clouddbformssql-dbserver_hachange_vpc_ko
  2. Enable to set Stand Alone if the existing high availability setting is Y, and high availability if the existing high availability setting N.
    • If changing to a high availability configuration, click and select whether to use a Multi Zone.
      When selected, 1 Primary DB and 1 Secondary DB are created in different zones to provide higher availability.
  3. Click [Yes].
  4. Check the status of the MSSQL Server from the MSSQL Server list on the DB Server screen.
    • Configuring: Status in which the MSSQL Server is being created and configured 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 the user, enabling the application server access to the MSSQL Server.

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.

Caution

The servers will restart when you upgrade server specifications. As access is unavailable during the restart, it is recommended to view the data after the restart is completed.

Note
  • The specifications change can only be done within the same type of MSSQL Server.
  • G3 servers can change specifications to a different server type.
  • The same task can be performed from View DB server details > Change DB specifications.

To change the specifications:

  1. When the Change DB Server specifications popup window appears, view the current server specifications.
  2. Click and select the server specifications you want to change to.
    clouddbformssql-dbserver_specChange_vpc_ko
  3. Click [OK].
  4. Check the status of the MSSQL Server with the specifications modified from the MSSQL Server list on the DB Server screen.
    • 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 server is available.

Manage DB Config

You can change Config Group to apply to MSSQL Server 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 on how to create, edit, and delete Config Groups, see Config Group.

Note

You can perform the same task from View DB server details > Manage DB Config.

To change:

  1. When the Change DB Config Group popup window appears, check the Config Group currently applied.
  2. Click and select the Config Group to change to.
    clouddbformssql-dbserver_dbConfig_vpc_ko
  3. Click [Change].
  4. Click the MSSQL Server with the changed Config Group from the MSSQL Server list on the DB Server screen.
  5. Click [Restart required] under Database Config.
  6. Check the status of the MSSQL Server from the MSSQL Server list on the DB Server screen.
    • 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.

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.

To set up or remove Public domain:

  1. When the Request public domain popup window appears, check the DB Server's name.
    • If you're to remove the Public domain assigned, the Remove Public domain popup window will appear. Check the DB Server name and Public domain.
      database-database-5-2_publicDomain_vpc_ko.png
  2. Click [Yes].

Manage DB user

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

Caution

The admin DB account cannot be changed. If you do change the DB account through SSMS, the use of some features will become restricted on the console.

Note

You can perform the same task from View DB server details > Manage DB user.

To change the password of an admin account:

  1. When the Manage DB user popup window appears, check the DB admin account.
  2. Enter the new password.
    * Enter 8 to 20 characters using at least 1 English letter, number, and special character.
    * The special characters ` & + ₩ " ' / or spaces can't be used
    clouddbformssql-dbserver_user_vpc_ko
  3. Click [Save].

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.

Note

The same task can be performed from View DB server details > Manage Database.

To add or delete databases:

  1. When the Manage Database popup window appears, check the database information.
  2. Add or delete databases.
    clouddbformssql-dbserver_db_vpc_ko
    • Add: Enter the database name to add to Database Name and then click [Add Database].
      • Enter between 1 and 20 characters using English letters, numbers, and the underscore (_) special character.
      • The first character must be an English letter.
    • Delete: Click [Delete] for the created database row.
  3. Click [Save].

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.

Note

The same task can be performed from View DB server details > Manage Backup settings.

To set up a backup retention period and backup time:

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

MSSQL Engine Upgrade

The MSSQL Engine minor version can be upgraded. The version upgrade is applied to the entire DB Service, and the upgrade is performed 1 server at a time in the following order: Slaves -> Mirror -> Principal. The server access is unavailable during the upgrade.

clouddbformssql_dbserver_upgrade_001_ko.png

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

Change DB service name

You can change the service name.
clouddbformssql_dbservername_edit

Manage Audit settings

  • You can leave a record of the DB server's logins and the creation, edit, and deletion of objects in the database (DDL).
  • When audit logging is enabled, the configuration applies to the entire DB cluster.
  • Audit information is created 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.

clouddbformssql_dbserver_audit_ko

  1. Click DB Management > DB Server details.
  2. In Manage Audit settings, change Audit to [Enable] and specify the desired config value.
  3. Click [Save].
  4. If there is a config value to be edited, change only the config value in enabled status and click [Save].
  5. When deleting a plugin, change the Audit value to [Disabled] and click [Save].
  • Audit Config variable list
Config Name (name of the config variable) Description
Policy Definition of an event to log to the audit log file.
Optims: ALL | LOGIN | DDL
  • ALL: LOGIN + DDL
  • LOGIN: Records access and failure of DB accounts accessing the DB.
  • DDL: Records DDL statements occurring in the DB.
    Changing the policy value does not automatically change any other config setting variables.
    		•
    MaxFileSize Maximum size of the audit log file.
    MaxRolloverFiles The number of files to keep among the rolled over audit log files.

    • 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.
      • You can note the last edited date of the auditlog file and download it to Object Storage from Download Log > Audit Log.

    • List of Audit Log fields

    Field name Description
    Time when event occurred Time when the event occurred.
    Log content The log file in XML format.
    • Include the following values as action values:
      • sqlserver.client_app_name
      • sqlserver.client_hostname
      • sqlserver.database_name
      • sqlserver.nt_username
      • sqlserver.sql_text
      • sqlserver.username
    • Depending on your audit option selection, include the following events field defaults:
      • sqlserver.error_reported
      • sqlserver.login
      • sqlserver.database_created
      • sqlserver.object_altered
      • sqlserver.object_created
      • sqlserver.object_deleted
    Note
    • Cached (accessed using Connection Pool recycling) logins are not recorded.
    • You can also perform the same setting operations in DB Server > DB Status > Manage Audit settings.
    • You can monitor the saved audit log files in real time under Monitoring > Audit Logs for each host.
    • You can download to Object Storage from DB Server > DB Status > Download Log > Audit Log.
    Caution

    Logs incur additional expenses for capacity by using DB Server data storage and the Cloud Log Analytics service.
    Additional fees apply when you subscribe to Object Storage. For more information about Object Storage and its pricing plans, see Services > Storage > Object Storage on the NAVER Cloud Platform portal.
    For the Japan Region, disable access control settings for the Object Storage bucket.

    Operating system management

    NAVER Cloud Platform regularly updates its server images, and details about update schedules and information for each operating system can be found in the portal's Notices. Operating system management provides a feature that allows the operating system to be upgraded to the latest version according to the server image update schedule. For detailed information on update versions, refer to the Windows Server release history OS build numbers and KB documentation.
    clouddbformssql-os_management_01_vpc_ko

    1. Click Manage DB > Manage operating system.
    2. After checking the operating system pre-check status, click [Next].
    Note
    • Operating system upgrades are available only for clusters configured with high availability. If you need to upgrade the operating system of a standalone server, change it to a high availability configuration first.
    • The operating system can be upgraded only when the database status, login synchronization status, and scheduler synchronization status of the currently running cluster are all in a completed state.

    clouddbformssql-os_management_02_vpc_ko

    1. Read the operating system management precautions and click [Yes, I agree to all.] .
    2. Click [Yes].
    Caution
    • When updating the operating system of the principal server to the latest version, the user must manually perform a failover in the console to proceed with subsequent steps in order to minimize service downtime. The execution time is the same as the time required when using the Restart with Failover feature.
    • After an operating system upgrade, you will not be able to view the monitoring data and event history of the servers from before the upgrade in the console. If you need to backup the monitoring data and event history prior to the upgrade, refer to the widget data download feature in the Cloud Insight user guide and the export log feature in the Cloud Log Analytics user guide.
    • Custom alert settings configured for the DB Cluster are not transferred automatically. If you have any manually configured alert items, reconfigure them after the OS update is complete.
    • Linked Server configurations are also not transferred automatically. Reconfigure the DB Server after the latest version OS update is complete.
    • After the OS update, the Private IP address will be changed. For Cloud DB for MSSQL, connecting to the DB using a private domain is recommended to prevent service impact even if the private IP changes. If you are using a private IP address, DB connection errors may occur after the OS update.

    Download Log

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

    clouddbformssql_dbserver_log_download1_ko

    Note

    You can perform the same download task from DB Server > DB Status > Download Log.

    Caution

    Additional fees apply when you subscribe to Object Storage. For more information about Object Storage and its pricing plans, see Services > Storage > Object Storage on the NAVER Cloud Platform portal.
    For the Japan Region, disable access control settings for the Object Storage bucket.

    Xe Baseline Log

    This log contains data collected to help you monitor and troubleshoot issues.
    This log enables the verification of details about internal tasks of the database engine related to performance monitoring and troubleshooting purposes.

    1. Export the log by sending it to Object Storage.
    2. Verify the XEL file in Object Storage to download it.

    clouddbformssql_dbserver_object_storage_ko

    1. Load the XEL file in SSMS.
    • English version: File > Open > Merge Extended Event Files > Add File.
    • Korean version: File > Open > Merge Extended Event Files > Add File.
      clouddbformssql_dbserver_ssms_xelfile_ko
    1. Click OK to make sure that the file has been loaded.
      clouddbformssql_dbserver_load_xelfile_ko
    Note

    Logs record Attention, Errors, queries causing locks for over 3 seconds, queries that need to be locked, causes for delays exceeding 100 ms, and all query logs with completion times over 2 seconds. A total of 20 MB * 50 log files are always stored.

    Name Timestamp of record
    RPC_COMPLETED
    SQL_BATCH_COMPLETED
    SP_STATEMENT_COMPLETED
    SQL_STATEMENT_COMPLETED

    To use the Xe Baseline Log for SQL monitoring in SSMS:

    1. Access the DB.
    2. Run the following query:
    SELECT TOP 10 convert(XML, event_data) AS StatementData
FROM sys.fn_xe_file_target_read_file(logName, NULL, NULL, NULL) //NCP_01_BASELINE_0_133704873120350000.XEL
    1. You can view using the created table.

    • To view in the order of the longest processing times.

      SELECT * FROM [DBO].[table name]
ORDER BY DURATION DESC

    • To view for a specific time period (with Timezone applied).

      WITH CTE AS  ( SELECT [TIMESTAMP] AT TIME ZONE 'KOREA STANDARD TIME' KST, 
       * FROM [TLOG] )  
SELECT CAST(DURATION / 1000. AS INT) MILISEC
    , [ATTACH_ACTIVITY_ID.GUID]
    , USERNAME
    , SQL_TEXT 
    , BATCH_TEXT
    , *
FROM CTE
WHERE KST >= '2024-09-09 15:30:58.7095570 +09:00'
    AND KST <= '2024-09-09 15:50:58.7095570 +09:00' 
    AND NAME IN ('RPC_COMPLETED', 'SQL_BATCH_COMPLETED', 'SP_STATEMENT_COMPLETED', 'SQL_STATEMENT_COMPLETED')
ORDER BY 1 DESC

    • To view using a GUID (obtained from a or b).

      SELECT * 
FROM [DBO].[table name]
WHERE [attach_activity_id.guid] = '7467F7A5-BF34-4EF7-BB72-596F90BBE908'
    Business Registration Number: 129-86-31394 E-commerce Permit Number:No. 2009-GyeonggiSeongnam-0510
    CEO: Kim Yuwon Address: NAVER Green Factory 17th–26th Floors, Buljeong-ro 6, Bundang-gu, Seongnam-si, Gyeonggi-do 13561, Republic of Korea. Customer Support Number: 1544-5876
    © NAVER Cloud Corp. All Rights Reserved.