This is the multi-page printable view of this section. Click here to print.
Microsoft SQL Server(DBaaS)
1 - Overview
Service Overview
Microsoft SQL Server(DBaaS) is a representative relational database management system (RDBMS) used in various applications. Samsung Cloud Platform provides an environment that can automate Microsoft SQL Server installation and perform management functions for operation through a web-based console.
Microsoft SQL Server (DBaaS) is designed with an Always On‑based availability architecture, so when the Primary server’s content changes, it is synchronously replicated to the Secondary server. Additionally, it provides an automatic backup feature at user-specified times to prepare for issues with the DB server or data, enabling recovery of data at the desired point in time.
Provided features
Microsoft SQL Server (DBaaS) provides the following features.
- Auto Provisioning (Auto Provisioning): UI allows installation and configuration of Database (DB), and provides a Primary-Secondary redundancy configuration built on Always On. * When the Primary server fails, it automatically fails over to the Secondary.
- Operation Control Management: Provides a function to control the status of running servers. * In addition to start and stop, a restart is possible if there is a DB issue or to apply configuration changes. * When high availability (HA) is configured, the node transition between Primary and Secondary can be performed directly by the user through a switch-over.
- Backup and Recovery: Provides data backup functionality based on its own backup commands. * Backup time slots and storage locations, as well as the day of full backups, can be set by the user, and additional fees may apply based on backup size. * It also provides a recovery feature for backed‑up data, so when a user initiates a recovery, a separate database is created and the recovery proceeds to the point in time selected by the user (the backup creation time or a user‑specified time). * When restoring to a user-specified point in time, you can set the restore point up to 5 minutes, 10 minutes, 30 minutes, or 1 hour before the stored backup and archive files.
- Version Management: Provides a Minor version upgrade feature based on some functionality improvements and security patches.
- Secondary configuration: It is possible to add a Read Replica (Secondary Replica) for read load balancing and disaster recovery (DR).
- Audit setting: Provides an Audit setting feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
- Parameter management: You can modify DB configuration parameters related to performance improvement and security.
- Service Status Query: Retrieves the final status of the current DB service.
- Monitoring: CPU, memory, performance monitoring information can be viewed through Cloud Monitoring and Servicewatch.
- DB User Management: View and manage the DB account (user) information registered in the DB.
- DB Log Export: You can export stored logs to the user’s Object Storage through Audit settings.
Components
Microsoft SQL Server(DBaaS) provides pre-validated engine versions and a variety of server types. Users can choose and use it based on the scale of the service they wish to configure.
Engine version
The engine versions supported by Microsoft SQL Server(DBaaS) are as follows.
Technical support is available until the supplier’s EoTS (End of Technical Service) date, and the EOS date when new creation is halted is set to six months before the EoTS date.
Since the EOS and EoTS dates may change according to the supplier’s policy, please refer to the supplier’s license management policy page for details.
- Microsoft SQL Server: https://learn.microsoft.com/ko-kr/lifecycle/products/?terms=sql%20server
| service | Provided version | Minor patch number / version | EoS Date (Samsung Cloud Plaform New Creation Stop Date) | EoTS date (Community technical support end date) |
|---|---|---|---|---|
| MS SQL Server | 2019 (Standard, Enterprise) | KB5033688 / 15.0.4355.3 | 2029-06 (planned) |
|
| 2019 (Standard, Enterprise) | KB5046365 / 15.0.4405.4 | 2029-06 (planned) |
| |
| 2019 (Standard, Enterprise) | KB5054833 / 15.0.4430.1 | 2029-06 (scheduled) |
| |
| 2019 (Standard, Enterprise) | KB5058722 / 15.0.4435.7 | 2029-06 (planned) |
| |
| 2022 (Standard, Enterprise) | KB5048033 / 16.0.4165.4 | 2032-06 (planned) |
| |
| 2022 (Standard, Enterprise) | KB5050771 / 16.0.4185.3 | 2032-06 (planned) |
| |
| 2022 (Standard, Enterprise) | KB5058721 / 16.0.4200.1 | 2032-06 (planned) |
| |
| 2022 (Standard, Enterprise) | KB5059390 / 16.0.4205.1 | 2032-06 (planned) |
| |
| 2022 (Standard, Enterprise) | KB5065865 / 16.0.4215.2 | 2032-06 (planned) |
|
The next version of MS SQL Server is scheduled to be available after September 2026. The actual service delivery schedule is subject to change.
- MS SQL Server 2022 (Standard, Enterprise) KB5078297 / 16.0.4236.2
Server type
The server types supported by Microsoft SQL Server (DBaaS) are as follows.
Please refer to Microsoft SQL Server(DBaaS) 서버 타입 for detailed information about the server types provided by Microsoft SQL Server (DBaaS).
Standard db1v2m4
| Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server types
|
| Server specifications | db1 | Provided server specifications
|
| Server specifications | v2 | vCore count
|
| Server specifications | m4 | Memory capacity
|
Preceding Service
This is a list of services that must be pre‑configured before creating the service. For detailed information, please refer to the guide provided for each service and prepare in advance.
| Service Category | service | Detailed description |
|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment |
1.1 - Server type
Microsoft SQL Server(DBaaS) server type
Microsoft SQL Server (DBaaS) provides server types composed of various combinations of CPU, memory, and network bandwidth. When creating a Microsoft SQL Server (DBaaS), the Database Engine is installed according to the server type selected for the intended use.
The server types supported by Microsoft SQL Server(DBaaS) are as follows.
Standard db1v2m4
Category | Example | Detailed description |
|---|---|---|
| Server type | Standard | Provided server type categories
|
| Server specifications | db1 | Provided server type classification and generation
|
| Server specifications | v2 | Number of vCores
|
| Server specifications | m4 | Memory capacity
|
db1 server type
The db1 server type of Microsoft SQL Server (DBaaS) is offered with standard specifications (vCPU, Memory) and is suitable for various database workloads.
- Intel 3rd Generation (Ice Lake) Xeon Gold 6342 Processor up to 3.3 GHz
- Supports up to 16 vCPUs and 256 GB of memory
- Maximum networking speed of 12.5 Gbps
| Category | Server type | vCPU | Memory | Network Bandwidth |
|---|---|---|---|---|
| Standard | db1v2m4 | 2 vCore | 4 GB | Up to 10 Gbps |
| Standard | db1v2m8 | 2 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v2m16 | 2 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v2m24 | 2 vCore | 24 GB | Maximum 10 Gbps |
| Standard | db1v2m32 | 2 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m8 | 4 vCore | 8 GB | Up to 10 Gbps |
| Standard | db1v4m16 | 4 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v4m32 | 4 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v4m48 | 4 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v4m64 | 4 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v6m12 | 6 vCore | 12 GB | Maximum 10 Gbps |
| Standard | db1v6m24 | 6 vCore | 24 GB | Up to 10 Gbps |
| Standard | db1v6m48 | 6 vCore | 48 GB | Up to 10 Gbps |
| Standard | db1v6m72 | 6 vCore | 72 GB | Up to 10 Gbps |
| Standard | db1v6m96 | 6 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m16 | 8 vCore | 16 GB | Up to 10 Gbps |
| Standard | db1v8m32 | 8 vCore | 32 GB | Up to 10 Gbps |
| Standard | db1v8m64 | 8 vCore | 64 GB | Up to 10 Gbps |
| Standard | db1v8m96 | 8 vCore | 96 GB | Up to 10 Gbps |
| Standard | db1v8m128 | 8 vCore | 128 GB | Up to 10 Gbps |
| Standard | db1v10m20 | 10 vCore | 20 GB | Up to 10 Gbps |
| Standard | db1v10m40 | 10 vCore | 40 GB | Up to 10 Gbps |
| Standard | db1v10m80 | 10 vCore | 80 GB | Up to 10 Gbps |
| Standard | db1v10m120 | 10 vCore | 120 GB | Up to 10 Gbps |
| Standard | db1v10m160 | 10 vCore | 160 GB | Up to 10 Gbps |
| Standard | db1v12m24 | 12 vCore | 24 GB | Up to 12.5 Gbps |
| Standard | db1v12m48 | 12 vCore | 48 GB | Up to 12.5 Gbps |
| Standard | db1v12m96 | 12 vCore | 96 GB | Up to 12.5 Gbps |
| Standard | db1v12m144 | 12 vCore | 144 GB | Up to 12.5 Gbps |
| Standard | db1v12m192 | 12 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v14m28 | 14 vCore | 28 GB | Up to 12.5 Gbps |
| Standard | db1v14m56 | 14 vCore | 56 GB | Up to 12.5 Gbps |
| Standard | db1v14m112 | 14 vCore | 112 GB | Up to 12.5 Gbps |
| Standard | db1v14m168 | 14 vCore | 168 GB | Up to 12.5 Gbps |
| Standard | db1v14m224 | 14 vCore | 224 GB | Up to 12.5 Gbps |
| Standard | db1v16m32 | 16 vCore | 32 GB | Up to 12.5 Gbps |
| Standard | db1v16m64 | 16 vCore | 64 GB | Up to 12.5 Gbps |
| Standard | db1v16m128 | 16 vCore | 128 GB | Up to 12.5 Gbps |
| Standard | db1v16m192 | 16 vCore | 192 GB | Up to 12.5 Gbps |
| Standard | db1v16m256 | 16 vCore | 256 GB | Up to 12.5 Gbps |
1.2 - Monitoring metrics
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Services by Resource
- New Resources: Resources created after the service improvement work in July 2026 are provided with monitoring using the ServiceWatch service by default.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition. *
Performance and log data backup, the settings configured by users linked with existing Cloud Monitoring (e. You must verify items such as event policies and perform tasks such as resetting the ServiceWatch service, then complete them.
Notice of the phased termination schedule for the Cloud Monitoring service
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch is available in the ServiceWatch Overview.
Microsoft SQL Server(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for Microsoft SQL Server (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
Please refer to the Virtual Server Monitoring Metrics guide for Microsoft SQL Server(DBaaS) server monitoring metrics.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Sessions in Active state | cnt |
| Active Transactions [Total] | Number of active transactions | cnt |
| Blocking Session ID | Long-running query (slow query) | ID |
| Connected Users | Number of users connected to the system | cnt |
| Datavolume Size [Free] | Available space | bytes |
| DBFiles [Not Online] | Run a query to verify that all data files are ONLINE. | cnt |
| Instance State [Cluster] | Status during MSSQL cluster configuration | state |
| Instance State [PID] | sqlservr.exe process pid | PID |
| Lock Processes [Blocked] | Number of SQL processes blocked by other processes | cnt |
| Lock Waits [Per Second] | Lock wait count per second | cnt |
| Page IO Latch Wait Time | Page IO latch waits average wait time | ms |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) | cnt |
| Slowquery CPU Time | CPU time spent executing SQL that runs for a long time (over 5 minutes) | ms |
| Slowquery Execute Context ID | Context ID linked to the execution task of a SQL that has been running for a long time (over 5 minutes) | ID |
| Slowquery Memory Usage | Memory usage incurred by the execution of SQL that runs for a long time (over 5 minutes) | bytes |
| Slowquery Session ID | Session ID of SQL queries running for a long time (over 5 minutes) | ID |
| Slowquery Wait Duration Time | Total wait time for wait type | ms |
| Tablespace Used | Data volume size | bytes |
| Transaction Time [MAX] | Long-running transaction | cnt |
1.3 - ServiceWatch metric
Microsoft SQL Server(DBaaS) sends metrics to ServiceWatch. The metrics provided by basic monitoring are data collected at 1‑minute intervals.
basic metrics
The following are basic metrics for the Microsoft SQL Server(DBaaS) namespace.
In the table below, the metrics whose names are shown in bold are the key metrics selected from those provided by Microsoft SQL Server (DBaaS). The main metrics are used to configure the service dashboards that are automatically built for each service in ServiceWatch.
Each metric provides guidance in the user guide on which statistical values are meaningful when viewing that metric, and among the meaningful statistics, the values displayed in bold are the primary statistics. In the service dashboard, you can view key metrics through primary statistical values.
OS Basic Metrics
Classification | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| CPU | CPU Usage | Percent | CPU usage |
|
| Disk | Disk Usage | Percent | Disk usage |
|
| Disk | Disk Write Bytes | Bytes/Second | Write capacity (bytes/second) on block device |
|
| Disk | Disk Read Bytes | Bytes/Second | Read throughput from block device (bytes/second) |
|
| Disk | Disk Write Requests | Count/Second | Number of write requests on block device (requests per second) |
|
| Disk | Disk Read Requests | Count/Second | Number of read requests on block device (requests per second) |
|
| Disk | Average Disk I/O Queue Size | None | Average queue length of requests issued to the block device |
|
| Disk | Disk I/O Utilization | Percent | The proportion of time the block device actually spent processing I/O operations |
|
| Memory | Memory Usage | Percent | Memory usage |
|
| Memory | Swap Out Bytes | Bytes/Second | Data transferred from memory to swap area (bytes/second) |
|
| Memory | Swap Used Bytes | Bytes | Current swap space size |
|
| Memory | Swap Cached Usage | Percent | Cached swap usage rate |
|
| Memory | Swap Total Bytes | Bytes | Total swap space size configured on the system |
|
| Memory | Swap In Bytes | Bytes/Second | Amount read from swap area to memory (bytes/second) |
|
| Memory | Swap Usage | Percent | Current usage ratio relative to total swap space |
|
| Memory | Swap Cached Bytes | Bytes | Size of pages that have been restored to memory but still have a copy in the swap area |
|
| Memory | Swap Free Bytes | Bytes | Size of unused remaining swap space |
|
| Network | Network In Bytes | Bytes/Second | Received capacity (bytes/second) on the network interface |
|
| Network | Network Out Bytes | Bytes/Second | Transmitted capacity (bytes/second) on the network interface |
|
| Network | TCP Connections | Count/Second | Total number of TCP connections currently established correctly |
|
| Network | Network In Packets | Count | Number of packets received on the network interface |
|
| Network | Network Out Packets | Count | Number of packets transmitted on the network interface |
|
| Network | Network In Dropped | Count | Number of packet drops received on the network interface |
|
| Network | Network Out Dropped | Count | Number of packet drops transmitted from the network interface |
|
| Network | Network In Errors | Count | Number of packet errors received on the network interface |
|
| Network | Network Out Errors | Count | Number of packet errors transmitted on the network interface |
|
| OS | OS Uptime | Seconds | Time elapsed (seconds) since the system was last booted |
|
Microsoft SQL Server(DBaaS) Basic Metrics
Classification | Performance items | unit | Detailed description | meaningful statistics |
|---|---|---|---|---|
| General | Page Life Expectancy Seconds | Seconds | Estimated time (seconds) that a data page remains in the buffer pool without disk re-reference |
|
| General | Full Scans/sec | Count/Second | Number of Table Full Scans per second |
|
| General | Range Scans/sec | Count/Second | Number of Range Scans performed per second |
|
| General | Index Searches/sec | Count/Second | Number of Index Searches performed per second |
|
| General | Buffer Cache Hit ratio | Percent | Proportion of page requests processed directly from the buffer cache |
|
| General | Cursor Requests/Sec | Count/Second | Number of SQL cursor requests received by the server per second |
|
| General | Page Fault Count | Count | Number of page faults for all processes, including system processes |
|
| Locks & Latches | Lock Requests/Sec | Count/Second | Number of lock requests per second |
|
| Locks & Latches | Lock Blocks | Count | Number of blocks where a lock occurred |
|
| Locks & Latches | Table Lock Escalation/Sec | Count/Second | The number of locked blocks per second became excessive, causing escalation to table-wide locking. |
|
| Locks & Latches |
| Count/Second | Dead Lock count per second |
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- up: 1
- down: 0
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
- Total
- Average
- Maximum
- Minimum
2 - How-to guides
Users can create the service by entering the required information for Microsoft SQL Server (DBaaS) and selecting detailed options through the Samsung Cloud Platform Console.
According to the policy of Samsung Cloud Platform, the Cloud Monitoring service is scheduled to be discontinued.
Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Resource-Specific Monitoring Service Application Guide
- New Resources: Resources created after the July 2026 service improvement work are provided with default monitoring using the ServiceWatch service.
- Existing resources: After the service improvement work in September 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, you must prepare for the Servicewatch transition. *
Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (e.g. Check the (event policy, etc.) and perform tasks such as resetting the ServiceWatch service, and complete them.
Cloud Monitoring Service Phased Termination Schedule Notice
- Console menu termination (September 2026 service improvement work)
- You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
- After the service ends in November, Cloud Monitoring data cannot be viewed. * Be sure to complete the ServiceWatch migration work within the parallel operation period**
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found by referring to ServiceWatch 개요.
Create Microsoft SQL Server(DBaaS)
You can create and use the Microsoft SQL Server (DBaaS) service from the Samsung Cloud Platform Console.
- Before creating the service, configure the VPC’s Subnet type as General.
- If the subnet type is Local, the corresponding Database service cannot be created.
- When loading more than 2 TB of large data, backups may take a long time or the database’s performance may degrade. * To prevent this, it is necessary to consider operational aspects such as cleaning unnecessary data or migrating old data to a statistical collection environment.
- This service is provided on a Single-AZ basis.
To create a Microsoft SQL Server(DBaaS), follow these steps.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) Create button. 2. Microsoft SQL Server(DBaaS) creation Navigate to the page.
- On the Microsoft SQL Server(DBaaS) Creation page, enter the information required to create the service and select detailed options.
- Select the required information in the Image and version selection area.
Category required statusDetailed description Image version Required Provide a version list of Microsoft SQL Server (DBaaS) Table. Microsoft SQL Server (DBaaS) Image and version selection options - Enter or select the required information in the Service Information Input area.
Category Required statusDetailed description Server name Prefix Required The server name where the DB will be installed - must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters (
-) with a length of 3 to 13 characters
- Based on the server name, a postfix such as 001, 002 is appended to create the actual server name
Cluster name Required Cluster name of the DB servers - Enter using English letters, 3 - 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Server type for DB installation - Standard: Standard specifications commonly used
- High Capacity: Large-capacity server with 24 vCores or more
- For detailed information about the server types provided by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) 서버 타입
Service Type > Planned Compute Selection Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute set
- Coverage Preview: Amount applied by Planned Compute per resource
- Create Planned Compute Service: Go to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Configure Block Storage used by the DB according to its purpose - Basic OS: Area where the DB engine is installed
- DATA: Storage area for table data, archive files, etc.
- After selecting the storage type, enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- SSD: High‑performance general volume
- HDD: General volume
- SSD_KMS, HDD_KMS: Additional encrypted volumes that use Samsung Cloud Platform KMS (Key Management System) encryption keys
- The configured storage type is also applied to additional storage
- Enter the capacity as a multiple of 8 within the range 16 to 5,120
- After selecting Use, enter the storage’s Purpose and Capacity
- After selecting the storage type, enter the capacity (see Block Storage 생성하기 for details on each Block Storage type)
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Redundant configuration Selection Redundancy configuration status - When redundancy configuration is used, the DB instance is configured as an Active DB and a Standby DB
Use AD Selection Set whether to use a pre-configured AD (Active Directory) server - Domain Name: Domain name
- Domain NetBIOS Name: Domain NetBIOS name
- DNS Server IP: Enter DNS server IP / secondary DNS server IP and click the Add button
- Up to 5 entries can be entered
- AD Server ID: AD user ID
- AD Server Password: User password
- High Availability Cluster Name: Name of the failover cluster used when configuring high availability
- Displayed only when the high availability option is used
- Click Port Connection Guide to view the Security Group inbound/outbound rule information required for connecting the SQL server and AD server
Network > Common Settings Required Network settings for servers created by the service - Select this when you want to apply the same settings to all installed servers
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Each server’s IP is generated automatically
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. Use when checked, you can select from reserved IPs in the VPC product’s Public IP. For more details, see Public IP 생성하기
Network > Server-specific Settings Required Network settings where servers generated by the service are installed - Select if you want to apply different settings for each installed server
- Select a pre‑created VPC, Subnet, IP, and Public NAT
- Enter the IP for each server
- The Public NAT feature is available only when the VPC is connected to an Internet Gateway. If you check Use, you can select from reserved IPs in the VPC product’s Public IP. For more information, see Public IP 생성하기
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy.
- Enter in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32), and click the Add button.
- To delete an entered IP, click the x button next to the entered IP.
maintenance period Selection DB maintenance window - If you select Use, you can set the day of the week, start time, and duration
- The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and patch tasks within that period are performed directly by the user.
- For the stable operation of the system, please set a maintenance window; we are not responsible for any issues arising from not setting it or from failure to perform tasks within the window.
Table. Microsoft SQL Server (DBaaS) service configuration items - must start with a lowercase English letter and be entered using lowercase letters, numbers, and special characters (
- Enter required database configuration information: enter or select the required information in this area.
Category Required statusDetailed description Database service name Required Database management unit name - starts with an uppercase English letter and is entered using English characters with a length of 1 - 15
Database name > default Required Server name applied during DB installation - must start with an English letter and be entered using English letters, numbers, and special characters (
.,_) with a length of 3 - 20 characters
Database name > Add Required Enter the Database name to install after selecting Use for the server name - . It must start with an English letter and be entered using English letters, numbers, and special characters (
.,_) with a length of 3 to 20 characters
- For each Database, the drive where data is stored can be selected from the drives added in Service Type > Block Storage
- Adding Databases is only possible in the Enterprise version, and up to 100 can be added
Database username Required DB user name - An account with the same name is also created on the OS
- Enter using lowercase English letters, 2 to 20 characters
- The following names cannot be used as Database user names
- root, user, sdscmpif, hacluster, adm, games, nobody, sshd, system, mail, postfix, sa, maxigent_cl
Database password Required DB connection password - English letters, numbers, and special characters(
“‘except) including, enter 8-30 characters
Check database password Required Check DB connection password - Re-enter the DB connection password identically
Database Port number Required DB connection port number - Enter DB port within the range 1200 - 65535
License Required SQL Server License Key - Enter the issued license key
- If the entered license key is invalid, the service may not be created
Backup > Use Selection Backup usage - Select Use to set the backup file retention period, backup start time, Full backup schedule (day of week), and Archive backup interval
Backup > Retention Period Selection Backup retention period - Select the backup retention period. Set the file retention period from 7 days to 35 days
- Backup files incur additional charges based on size
Backup > Backup Start Period Selection Backup start time - Select backup start time
- The minutes (minutes) at which the backup runs are set randomly, and the backup end time cannot be configured
Backup > Full backup schedule (day of week) Selection Full backup schedule - Select the day of the week for full backup execution
- Full backup is performed on a weekly basis
Backup > Archive backup schedule Selection Archive backup frequency - Select the Archive backup frequency
- The Archive backup frequency is recommended at 1 hour. Selecting 5 minutes, 10 minutes, or 30 minutes may affect DB performance
Audit Log Settings Selection Whether to store Audit Log - Select Use to enable the Audit Log feature
- DDL and user connection information records are stored
- Enabling Audit may degrade DB performance
ServiceWatch log collection Selection ServiceWatch log collection status - Select Use to configure the ServiceWatch log collection feature
- Provided free up to 5 GB for all services within the Account, and charges apply based on storage size for usage exceeding 5 GB
- When collecting, log groups and log streams are created automatically, and they cannot be deleted until the resource is deleted
- To prevent exceeding 5 GB, it is recommended to delete log data directly or shorten the retention period
Parameter Required DB configuration parameters - Click the View button to view detailed information of the parameters
- Parameters can be modified after the service creation is complete, and a DB restart is required after modification
DB Collation Selection Data sorting method - Data sorting, a command that specifies the method of comparison, can produce different results depending on the settings
Time zone Required Standard time zone used by the database Table. Microsoft SQL Server (DBaaS) Database configuration items - In the Additional Information Input area, enter or select the required information.
Category Required statusDetailed description tag Selection Add Tag - Up to 50 per resource can be added
- After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) Additional Information Input Items
- Select the required information in the Image and version selection area.
- Summary Verify the detailed information and estimated charges generated in the panel, then click the Create button.
- Once creation is complete, check the created resource on the Resource List page.
Microsoft SQL Server(DBaaS) Check detailed information
The Microsoft SQL Server (DBaaS) service allows you to view and edit the full list of resources and detailed information. Microsoft SQL Server(DBaaS) Details The page consists of Details, Secondary(DR) Information, Tags, Activity History tabs, and for databases with a configured Secondary(DR), an additional Secondary(DR) Information tab is provided.
To view detailed information about the Microsoft SQL Server (DBaaS) service, follow these steps.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Click the resource to view detailed information on the page. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Microsoft SQL Server(DBaaS) Details At the top of the page, status information and details about additional features are displayed.
Category Detailed description Cluster status Cluster status with DB installed - Creating: Cluster is being created
- Editing: Cluster is transitioning to an operational state
- Error: Cluster encountered a failure while performing a task
- If this persists, contact the administrator
- Failed: Cluster failed during creation
- Restarting: Cluster is being restarted
- Running: Cluster is operating normally
- Starting: Cluster is being started
- Stopped: Cluster is stopped
- Stopping: Cluster is stopping
- Synchronizing: Cluster is being synchronized
- Terminating: Cluster is being terminated
- Unknown: Cluster status is unknown
- If this persists, contact the administrator
- Upgrading: Cluster is being upgraded
Cluster control Buttons to change the cluster state - Start: Start a stopped cluster
- Stop: Stop a running cluster
- Restart: Restart a running cluster
- Switch-Over: Switch a standby cluster to Active
View more add-ons Cluster management buttons - Service status synchronization: Retrieve real-time DB service status
- Backup history: If backup is configured, verify successful execution and view the backup history
- Database recovery: Restore the DB based on a specific point in time
- Parameter management: View and modify DB configuration parameters
- Secondary configuration: Configure a read‑only cluster as Secondary (DR)
- Secondary configuration (Other-Region): Configure a disaster‑recovery Secondary in another region; if the account has no region to configure, the button is disabled
- DB user management: View and manage DB accounts (users) registered in the DB
- Export DB Log: Logs stored via Audit settings can be exported to the user’s Object Storage
- Primary promotion: Promote a Secondary (DR) to Primary to ensure DB service continuity
Service cancellation Cancel Service button Table. Microsoft SQL Server (DBaaS) status information and additional features
- Microsoft SQL Server(DBaaS) Details At the top of the page, status information and details about additional features are displayed.
Detailed Information
Microsoft SQL Server (DBaaS) List page allows you to view detailed information of the selected resource and, if necessary, edit the information.
| Category | Detailed description |
|---|---|
| Server Information | Server information configured in this cluster
|
| service | Service name |
| Resource Type | Resource Type |
| SRN | Unique resource ID in Samsung Cloud Platform
|
| Resource Name | Resource name
|
| Resource ID | Unique resource ID in the service |
| Constructor | User who created the service |
| Creation Date/Time | Service creation date and time |
| Modifier | User who edited the service information |
| Modification date and time | Date and time the service information was modified |
| Image version | Installed DB image and version information
|
| Cluster name | Cluster name of the configured servers |
| Databse service name | Database Management Unit Name |
| Database username | DB user name |
| Database name > Default Database | Server name applied during DB installation |
| Database name > Add Database | Server name applied during DB installation
|
| Planned Compute | Resource status with Planned Compute set
|
| Maintenance period | DB Maintenance Period Status
|
| Backup | Backup configuration status
|
| Audit Log configuration | Audit Log configuration status
|
| ServiceWatch log collection | ServiceWatch Log Collection Configuration Status
|
| time zone | Standard time zone used by the database |
| DB Collation | Data sorting method |
| AD information | Server AD information |
| VIP | Virtual IP information
|
| Network | Network information (VPC, Subnet) of the installed DB |
| IP access control | Service access policy configuration
|
| Primary & Secondary | Primary/Secondary server type, base OS, additional Disk information
|
Secondary(DR) information
Secondary(DR) Information tab is enabled only when Secondary(DR) is configured. Secondary(DR) Information Through the tab, you can view the Master cluster name, the number of Secondary(DR), and the status of Secondary(DR).
| Category | Detailed description |
|---|---|
| Primary information | Name of the primary cluster |
| Secondary (DR) count | Number of Secondary (DR) created in the Primary cluster |
| Secondary(DR) status | Status of the Secondary (DR) server created in the Primary cluster
|
Tag
Microsoft SQL Server (DBaaS) List page allows you to view the tag information of the selected resource, and to add, modify, or delete it.
| Category | Detailed description |
|---|---|
| Tag list | Tag list
|
Job History
Microsoft SQL Server(DBaaS) List You can view the operation history of the selected resource on the page.
| Category | Detailed description |
|---|---|
| Task History List | Resource Change History
|
Managing Microsoft SQL Server (DBaaS) Resources
If you need to change the existing configuration options of a created Microsoft SQL Server (DBaaS) resource, recover it, or manage parameters, you can perform the tasks on the Microsoft SQL Server(DBaaS) Details page.
Operation Control
If changes occur to a running Microsoft SQL Server (DBaaS) resource, you can start, stop, or restart it. Also, when HA is configured, you can switch between Primary and Secondary servers via a switch‑over.
To control the operation of Microsoft SQL Server (DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to control its operation. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Check the status of Microsoft SQL Server(DBaaS) and complete the change using the control button below.
- Start: DB service is installed on the server and the DB service is running (Running).
- Stop: The server where the DB service is installed and the DB service will be stopped (Stopped).
- Restart: Only the DB service will be restarted.
- Switch Over: You can switch the DB’s Primary server and Secondary server.
Synchronize service status
You can synchronize the real-time service status of Microsoft SQL Server (DBaaS).
To view the service status of Microsoft SQL Server(DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to view the service status. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Service Status Synchronization button. 4. While it is being queried, the cluster changes to Synchronizing state.
- Once the query completes, the status in the server information item is updated, and the cluster changes to Running state.
Change Server Type
The configuration can be changed.
To change the server type, follow these steps.
- If you modify the server type, a server restart is required. * Please verify separately any software license modifications or software settings and their implementation due to server specification changes.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Edit icon for the server type you want to change at the bottom of the detailed information. 4. Edit Server Type The popup window opens.
- Edit Server Type In the popup window, select the server type, then click the Confirm button.
Add storage
If you need more than 5 TB of data storage, you can add additional storage. In a redundant DB setup, all redundant servers are added simultaneously.
To add storage capacity, follow the steps below.
- It is applied in the same way as the Storage type selected when creating the service.
- For a high‑availability configured DB, adding storage is applied simultaneously to the storage of the Primary DB and the Secondary DB.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Add Disk button at the bottom of the detailed information. 4. Additional Storage Request The popup window opens.
- Additional Storage Request In the popup window, after entering the purpose and capacity, click the Confirm button.
Expanding Storage
Storage added to the data area can be expanded up to a maximum of 5 TB based on the initially allocated capacity. In a redundant DB setup, all redundant servers are expanded simultaneously.
To increase storage capacity, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server(DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to change the server type. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Edit icon for the additional Disk you want to add at the bottom of the detailed information. 4. Edit Additional Storage popup opens.
- Edit Additional Storage After entering the expansion capacity in the popup window, click the Confirm button.
Terminate Microsoft SQL Server(DBaaS)
You can cancel unused Microsoft SQL Server (DBaaS) to reduce operating costs. However, terminating the service may cause the currently operating service to stop immediately, so you should proceed with the termination only after fully considering the impact of any service interruption.
To cancel Microsoft SQL Server(DBaaS), follow the steps below.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Select the resource to cancel on the page, and click the Cancel Service button.
- After termination is complete, verify that the resource has been terminated on the Microsoft SQL Server(DBaaS) list page.
2.1 - Managing DB Services
Users can manage Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console.
Managing Database
For the Microsoft SQL Server Enterprise edition, you can add a new database. You can add up to 100 per cluster.
Add Database
To add a Database, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Add button for the Database name field. 4. Add Database The popup window opens.
- Add Database In the popup window, click the + button to enter the database name and select a drive, then click the Confirm button.
Delete Database
To delete the Database, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to add storage. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Edit button for the Database name field. 4. Delete Additional Database A popup window opens.
- Delete added Database In the request popup, check the Database you want to delete and click the Delete button. 5. Database Delete The popup window opens.
- Delete Database In the popup window, after entering the name of the Database you want to delete, click the Confirm button.
Managing Parameters
Provides a feature that allows you to easily view and modify database configuration parameters.
View Parameter
To view configuration parameters, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to view or modify parameters. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the More button, then click the Parameter Management button. 4. Parameter Management The popup window opens.
- In the Parameter Management popup, click the Search button. 5. The Lookup Notification popup window opens.
- When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
Edit Parameter
To modify the configuration parameters, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page whose parameters you want to view and modify. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the More button, then click the Parameter Management button. 4. Parameter Management popup window opens.
- Parameter Management In the popup window, click the Search button. 5. View Notification A popup window opens.
- When the View Notification popup appears, click the Confirm button. 6. Retrieving may take a short amount of time.
- If editing is required, click the Edit button and enter the changes in the custom value field of the Parameter to be edited.
- When the input is complete, click the Done button.
Manage DB Users
Provides functionality to view and manage DB user information.
Query DB Users
To look up DB users, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource whose DB users you want to view. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the More button and then click the DB User Management button. 4. Navigate to the DB User Management page.
- On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
Changing DB User Status
To change the status of the retrieved DB user, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource for which you want to edit the DB user. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the More button, then click the DB User Management button. 4. Go to the DB User Management page.
- On the DB User Management page, click the Search button. 5. Retrieving may take a short amount of time.
- If modification is required, click the Edit button, and change the status area value or enter remarks.
- When the input is complete, click the Complete button.
Modify Audit Settings
You can modify the Audit log storage settings for Microsoft SQL Server (DBaaS).
To change the Audit log storage settings of Microsoft SQL Server(DBaaS), follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- Click the Microsoft SQL Server(DBaaS) menu on the Service Home page. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server (DBaaS) List Click the resource to view the service status on this page. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Edit icon of Audit Settings at the bottom of the detailed information. 4. Audit Settings Modification The popup window opens.
- Audit Settings Modification After modifying the usage in the popup window, click the Confirm button.
- When Use is selected, the Audit log feature is enabled. * Enabling audit logging may degrade database performance.
- If you disable usage, the Audit log storage file will be deleted. * Back up the Audit log file separately before disabling.
Export DB Log
Supports exporting log data that requires long-term retention among audit (Audit) logs to Object Storage. Users can directly configure the log types that need to be stored, the destination Bucket for export, and the log export interval. Copies logs to the specified Object Storage for retention according to the configured criteria. Additionally, to efficiently manage disk space, we also provide an option that exports logs to Object Storage while automatically deleting the original log files. By using this option, you can effectively free up storage capacity while safely retaining the necessary log data for the long term.
- To use the DB Log export feature, you need to create an Object Storage. * To create Object Storage, please refer to the Object Storage 사용자 가이드.
- Please be sure to verify the expiration date and time of the authentication key. * If the authentication key expires, logs will not be stored in the bucket.
- Please ensure that authentication key information is not exposed to external parties.
Setting the DB Log export mode
To set the DB Log export mode, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to export the DB Log. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the More button, then click the Export DB Log button. 4. Export DB Log Go to the page.
- Click the Register button on the DB Log Export page. 5. Go to the DB Log Export Registration page.
- On the DB Log Export Registration page, after entering the required information, click the 완료 button.
Category Required Detailed descriptionLog type Required Log type to be saved Save bucket name Required Object Storage bucket name to be saved Authentication key > Access key Required Access key for accessing the Object Storage you want to store Authentication key > Secret key Required Secret key for accessing the Object Storage you want to store File creation cycle Required File creation frequency in Object Storage Whether to delete the original log Selection Whether to delete the original logs when exporting to Object Storage Table. Microsoft SQL Server (DBaaS) DB Log Export Configuration Items
Manage DB Log Export
To modify, cancel, or immediately export the DB Log export settings, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List Click the resource on the page for which you want to manage DB Log export. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the More button, then click the DB Log Export button. 4. Export DB Log Go to the page.
- On the DB Log Export page, depending on the log type you want to manage, click the More button and then click the Export Now, Edit, Terminate buttons.
- Export Immediately: The selected logs are exported to the bucket of the previously configured Object Storage.
- Edit: Modify the DB Log export mode setting.
- Cancel: Cancel the DB Log export mode setting.
Minor version upgrade
Provides version upgrade functionality due to feature enhancements and security patches. Only minor version upgrades are supported within the same major version.
- First retrieve the service status via service status synchronization, then proceed with the version upgrade.
- It is recommended to perform an immediate backup in advance to prepare for any issues that may arise during the upgrade process. * If not, a failure may occur and some data may not be recoverable.
- In a DB configured with Secondary(DR), the Primary DB version cannot be higher than the Secondary(DR) version. * First check the version of the Secondary (DR), and if necessary, perform a version upgrade.
- The backed-up data is automatically deleted after the version upgrade is completed.
To perform a minor version upgrade, follow the steps below.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource to upgrade the version. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Edit button of the Image version item. 4. Version Upgrade A popup window opens.
- Version Upgrade In the popup, select the updated version and whether to enable backup, then click the Confirm button.
- Version Upgrade Notification Click the OK button in the popup window.
2.2 - Backing up and restoring the DB
Users can configure backups of Microsoft SQL Server (DBaaS) through the Samsung Cloud Platform Console and restore from the backed‑up files.
Microsoft SQL Server(DBaaS) Backup
Microsoft SQL Server (DBaaS) provides a data backup feature based on its own backup commands. Additionally, it provides an optimized backup environment for data protection and management through backup history verification and backup file deletion features.
Configure Backup
For instructions on configuring backup settings for Microsoft SQL Server (DBaaS), see the Microsoft SQL Server(DBaaS) 생성하기 guide.
To modify the backup settings of the created resource, follow the steps below.
When a backup is configured, it runs at the designated time after the set schedule, and additional fees are incurred based on the backup volume.
- If you change the backup setting to Unset, backup execution will stop immediately, and the stored backup data will be deleted and can no longer be used.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource you want to configure backup for. 3. Microsoft SQL Server(DBaaS) Details Go to the page.
- Click the Edit button of the backup item. 4. Backup Settings The popup window opens.
- When configuring a backup, click Use in the Backup Settings popup, select the retention period, backup start time, and Archive backup interval, then click the Confirm button.
- If you want to stop the backup setting, uncheck Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone.
Once user authentication is completed, the backup setting is disabled and backup execution stops.
- If you want to stop the backup setting, uncheck Use in the Backup Settings popup window and authenticate via the logged-in user’s mobile phone.
Perform immediate backup
If additional data protection is needed, you can quickly create a backup using the instant backup feature.
To perform an immediate backup, follow these steps.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List page, click the resource to perform an immediate backup. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Immediate Backup button of the backup item. 4. Immediate backup settings popup window opens.
- In the Immediate Backup Settings popup, click the Confirm button.
Check backup history
To view the backup history, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Navigate to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) List Click the resource to view the backup history on the page. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Backup History Click the button. 4. Backup History The popup window opens.
- Backup History In the popup window, you can view the backup status, version, backup start time, backup completion time, and size.
Delete backup file
To delete the backup history, follow these steps.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- On the Microsoft SQL Server(DBaaS) List page, click the resource to view the backup history. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Backup History button. 4. Backup History The popup window opens.
- Backup History In the popup window, check the files you want to delete, then authenticate using the logged-in user’s mobile phone.
- When user authentication is completed, the backup file will be deleted.
Recover Microsoft SQL Server(DBaaS)
If a failure or data loss requires restoration from a backup file, recovery can be performed based on a specific point in time using the recovery feature. When you perform a Microsoft SQL Server(DBaaS) recovery, a new server is created with the OS image from the initial provisioning point, the database is installed with the version from the backup point, and the recovery proceeds using the database’s configuration information and data.
To restore Microsoft SQL Server(DBaaS), follow these steps.
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Go to the Microsoft SQL Server(DBaaS) List page.
- Microsoft SQL Server(DBaaS) Resource On the list page, click the resource you want to recover. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Database Recovery button. 4. Database Recovery Navigate to the page.
- After entering the relevant information in the Database Recovery Configuration area, click the Complete button.
Category required statusDetailed description Recovery type Required Set the point in time the user wants to recover - Backup point (recommended): Recover based on the backup file. Select from the list of backup points displayed in the list
- Custom point: Recover to a user‑desired point within the range of recoverable backup times. The recoverable period depends on the Archive backup schedule setting, allowing recovery to 1 hour/30 minutes/10 minutes/5 minutes before the current time from the initial backup start point. Select the date and time to back up
Server name prefix Required Recovery DB server name - must start with a lowercase English letter and may include lowercase letters, numbers, and special characters (
-) using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters using 2~16 characters and between 2~16 characters between 2~16 characters between 2~16 characters 2~ Recovery DB server name
Cluster name Required Recovery DB cluster name - Enter using English letters, 3 ~ 20 characters
- A cluster is a unit that groups multiple servers
Service Type > Server Type Required Recovery DB server type - Standard: standard specifications commonly used
- High Capacity: large-capacity server of 24 vCore or more
Service Type > Planned Compute Selection Status of resources with Planned Compute set - In Use: Number of resources with Planned Compute that are currently in use
- Configured: Number of resources with Planned Compute set
- Coverage Preview: Amount applied per resource by Planned Compute
- Create Planned Compute Service: Go to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Service Type > Block Storage Required Block Storage settings used by the recovery DB - Basic OS: Area where the DB engine is installed
- DATA: Data storage area
- Applied identically with the storage type set in the original cluster
- Enter capacity as a multiple of 8 within the range 16 to 5,120
- Additional: Data storage area
- Applied identically with the storage type set in the original cluster
- In the recovery DB, only DATA and TEMP purposes can be added
- After selecting Use, enter the storage purpose and capacity
- To add storage, click the Add button; to delete, click the x button
- Capacity can be entered as a multiple of 8 within the range 16 to 5,120, and up to 9 can be created
Use AD Selection Preconfigured AD (Active Directory) server usage setting - AD Server ID: AD User ID
- AD Server Password: User Password
Database username Required Database username - Apply the same username set in the original cluster
Database Port number Required Database Port number - Apply the same Port number as configured in the original cluster
IP access control Selection Service Access Policy Configuration - Since the access policy is set for the IP entered on the page, you do not need to configure a separate Security Group policy
- Enter the IP in IP format (example:
192.168.10.1) or CIDR format (example:192.168.10.0/24,192.168.10.1/32) and click the Add button
- To delete an entered IP, click the x button next to the IP
Maintenance period Selection DB maintenance window - If you select Use, you can set the day of the week, start time, and duration
- The maintenance window is a feature that allows the user to set the time slot for performing patch operations, and any patch work within that period is performed directly by the user.
- We ask you to set a maintenance window for the stable operation of the system, and we are not responsible for any issues arising from not setting it or from failure to perform within the window.
tag Selection Add Tag - After clicking the Add Tag button, enter or select Key, Value values
Table. Microsoft SQL Server (DBaaS) recovery configuration items
2.3 - Add Secondary
The user can enter the required information for Secondary through the Samsung Cloud Platform Console and create the service using detailed options.
Add Secondary
Through secondary configuration, you can create replica servers for read‑only or disaster‑recovery purposes. To add a Secondary, it must be created with HA redundancy configuration and Enterprise Edition, and the backup feature must be enabled.
To set up Secondary, follow these steps.
- Click the All Services > Database > Microsoft SQL Server(DBaaS) menu. 1. Navigate to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Go to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to configure Secondary. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the Add Secondary button. 4. Go to the Secondary Add page.
- After entering information in the Secondary configuration area, click the Create button.
Category Required statusDetailed description Region Required Region to configure Secondary (DR) - Secondary configuration (Other Region) shown only when selected
Secondary number Required Number of Secondary to configure - Only one can be configured per cluster
Secondary name Required Secondary server name - must start with a lowercase English letter, and using lowercase letters, numbers, and special characters (
-) be entered with 3 ~ 15 characters
- The entered Secondary name is displayed as the cluster name in the list
Service Type > Server Type Required Secondary server type - Apply the same as the server type set in the source DB
Service Type > Planned Compute Selection Status of resources with Planned Compute configured - In Use: Number of resources with Planned Compute configured that are currently in use
- Configured: Number of resources with Planned Compute configured
- Coverage Preview: Amount applied by Planned Compute per resource
- Create Planned Compute Service: Go to the Planned Compute service application page
- For more details, see Planned Compute 신청하기
Network > Common Settings Essential Network settings where the servers created by the service are installed - applied identically to the network settings configured in the original DB
Network > Server Settings Required Network settings for servers created in the service - Select when you want to apply different settings per installed server
- Apply the same as the network settings configured in the original DB
- When setting per server
10.10.10.0/24enter an IP address within the range
License Required SQL Server License Key - Enter the issued license key.
- If the entered license key is invalid, the service may not be created.
AD(Active Directory) Selection Enter AD information entered when creating the service - AD Server ID: AD User ID
- AD Server Password: User Password
Table. Microsoft SQL Server (DBaaS) Secondary configuration items
Promoting Secondary (DR) to Primary
You can promote a configured Secondary (DR) to Primary.
To promote Secondary(DR) to Primary, follow these steps.
- All Services > Database > Microsoft SQL Server (DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) menu. 2. Microsoft SQL Server(DBaaS) List Navigate to the page.
- Microsoft SQL Server(DBaaS) List On the page, click the resource to promote to Primary. 3. Microsoft SQL Server(DBaaS) Details Navigate to the page.
- Click the More button, then click the Primary Promotion button. 4. Primary Promotion Notification The popup window opens.
- Primary Promotion Notification In the popup window, click the Confirm button.
2.4 - Microsoft SQL Server(DBaaS) server connection
Scenario Overview
Microsoft SQL Server(DBaaS) server connection The scenario involves creating a Bastion host (Virtual Server) and a Database service, and accessing the DB service through the Bastion host. To reliably connect to Microsoft SQL Server (DBaaS) in the Samsung Cloud Platform environment, you need to create a Bastion host and establish a network connection using it. To maintain stability and a high level of security, we recommend configuring the Database service in a Private Subnet environment and setting up the Bastion host in a restricted Public Subnet environment.
This scenario primarily describes creating a Bastion host and Database service, configuring the network environment for Bastion host and Database access, and connecting through a DB client.
Scenario components
You can build the scenario using the following services.
| Service group | service | Detailed description | |
|---|---|---|---|
| Networking | VPC | A service that provides an isolated virtual network in a cloud environment | |
| Networking | VPC > Subnet | A service that lets users segment the network within a VPC to match their purpose and scale | |
| Networking | VPC > Public IP | A service that reserves a public IP and allocates and releases it to Compute resources. | |
| Networking | VPC > Internet Gateway | A service that connects VPC resources to the Internet | |
| Networking | Security Group | Virtual firewall that controls server traffic | |
| Database | Microsoft SQL Server(DBaaS) | A service that easily creates and manages Microsoft SQL Server in a web environment | |
| Compute | Virtual Server | Virtual server optimized for cloud computing | |
| Compute | Virtual Server > Keypair | Encryption file used to connect to the Virtual Server |
- Since the default policy of the Security Group is Deny All, you must register only the allowed IPs.
- The All Open(Any IP, Any Port) policy for In/Outbound can expose cloud resources directly to external threats.
- By specifying the required IP and Port and setting a policy, you can strengthen security.
Scenario setup method
Create the services needed to build the scenario by following the procedure below.
1. ## Configure Network
Describes the process of configuring the network environment for accessing the Bastion Host and Database services.
1-1. ### Create VPC
- All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Create VPC button. 2. Go to the Create VPC page.
- On the VPC creation page, enter the information required to create the service.
- Enter the IP range as
192.168.x.0/16.
- Enter the IP range as
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the VPC List page.
1-2. ### Create Subnet
- All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Subnet menu. 2. Go to the Subnet list page.
- Create Subnet Click the button. 3. Go to the Subnet Creation page.
- On the Subnet Creation page, enter the information required to create the service.
- Select the Subnet type as General.
- Select a pre‑created VPC.
- Enter the IP range as
192.168.x.0/24.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Subnet List page.
1-3. ### Create Internet Gateway
- All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Internet Gateway menu. 2. Go to the Internet Gateway List page.
- Internet Gateway creation Click the button. 3. Go to the Create Internet Gateway page.
- On the Internet Gateway Creation page, enter the required information needed to create the service.
- Select a pre‑created VPC.
- In the Firewall usage option, select Use.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- Once creation is complete, check the created resource on the Internet Gateway List page.
1-4. ### Create Public IP
- All Services > Networking > VPC Click the menu. 1. Navigate to the VPC’s Service Home page.
- On the Service Home page, click the Public IP menu. 2. Go to the Public IP List page.
- Public IP reservation Click the button. 3. Go to the Public IP reservation page.
- On the Public IP reservation page, enter the required information for service reservation.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resources on the Public IP List page.
1-5. ### Create Security Group
- Click the All Services > Networking > Security Group menu. 1. Go to the Service Home page of the Security Group.
- On the Service Home page, click the Create Security Group button. 2. Go to the Security Group Creation page.
- On the Security Group creation page, enter the required information to create the service.
- Check the input information and click the Done button.
- After creation is complete, verify the created resources on the Security Group List page.
2. ## Create Bastion host
Explains the process of configuring a Bastion Host that requires the Database access client to be installed.
2-1. ### Create Server Keypair
- All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Keypair menu. 2. Go to the Keypair List page.
- Create Keypair button, click it. 3. Go to the Keypair creation page.
- On the Keypair Creation page, enter the required information needed to create the service.
- Verify the creation information and click the Complete button.
- The key can be downloaded only for the first time, and reissuance is not provided.
- Please store the downloaded key in a secure location.
2-2. ### Create Bastion host
- Click the All Services > Compute > Virtual Server menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Create Virtual Server button. 2. Go to the Create Virtual Server page.
- On the Virtual Server Creation page, enter the required essential information needed to create the service.
- Select Windows for the image.
- Select the pre-created VPC and Subnet.
- Click Use NAT, and select the reserved Public IP from 1-4. Public IP 생성하기.
- Connect the Keypair created in 2-1. Create Server Keypair.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- When creation is complete, check the created resources on the Virtual Server list page.
2-3. ### Check Bastion host login ID and PW
- All Services > Compute > Virtual Server Click the menu. 1. Navigate to the Service Home page of the Virtual Server.
- On the Service Home page, click the Virtual Server menu. 2. Go to the Virtual Server List page.
- Virtual Serve List page, click the resource you created in 2-2. Bastion host 생성하기. 3. Go to the detailed information page for the resource.
- Click the RDP password view button in the Keypair name field on the detail information page. 4. RDP password lookup A popup window opens.
- RDP password lookup in the popup window, attach the keypair file downloaded from 2-1. 서버 Keypair 생성하기.
- After attaching, click the Password verification button. 6. The ID and password required to access the resource are displayed.
- The ID and Password are used later as credentials to access the Bastion host in 5-1. Bastion host 접속하기.
3. ## Create Database
Describes the process of creating a Database service.
3-1. ### Create Microsoft SQL Server(DBaaS) Service
- All Services > Database > Microsoft SQL Server(DBaaS) Click the menu. 1. Go to the Service Home page of Microsoft SQL Server (DBaaS).
- On the Service Home page, click the Microsoft SQL Server(DBaaS) Create button. 2. Microsoft SQL Server(DBaaS) Creation Navigate to the page.
- Microsoft SQL Server(DBaaS) Creation page, enter the required information to create the service.
- Select the pre‑created VPC and Subnet and connect them.
- Enter database-related creation information on the required information input screen.
- Add the Bastion host IP in the IP access control item.
- The database port defaults to 2866, but users can also specify a different one.
- Summary Check the detailed information and estimated billing amount generated in the panel, and click the Complete button.
- After creation is complete, check the created resource on the Microsoft SQL Server(DBaaS) list page.
4. ## Configure Rules
Describes the process of setting rules for a user to connect to the Bastion host and rules for connecting to the Database from the Bastion host.
4-1. ### Security Group Add security rule
- Click the All Services > Networking > Security Group menu. 1. Go to the Service Home page of the Security Group.
- On the Service Home page, click the Security Group menu. 2. Navigate to the Security Group List page.
- 1-5. 3. Security Group CreateSelect the Security Group resource created in 3. Go to the detailed information page for the resource.
- On the detail information page, click the Rules tab. 4. Go to the Rules tab.
- Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
Direction Remote Target address Protocol Port Explanation Inbound CIDR User PC IP TCP 3389 (RDP) Bastion access PC → Bastion host Outbound CIDR DB IP TCP Database Port (manual entry) Bastion host → Database Table. Security Group rules that need to be added
4-2. ### Add IGW Firewall rule
- All Services > Networking > FirewallClick the menu. 1. Navigate to the Firewall’s Service Home page.
- On the Service Home page, click the Firewall menu. 2. Go to the Firewall List page.
- On the Firewall List page, select the Internet Gateway resource name created in 1-3. Internet Gateway 생성하기. 3. Go to the detailed information page for the resource.
- On the detail information page, click the Rules tab. 4. Go to the Rules tab.
- Click the Add Rule button on the Rule tab. 5. Add Rule Navigate to the popup window.
- Add Rule In the popup window, enter the rule below, and click the Confirm button.
Origin address Destination address Protocol Port Operation Direction Explanation Bastion connection PC IP Bastion host IP TCP 3389(RDP) Allow Inbound User PC → Bastion host Table. Internet Gateway Firewall rules to be added
5. ## Database Connect
Describes the process of a user connecting to a database through a DB client program.
This guide provides instructions on how to connect using SSMS (Microsoft SQL Server Management Studio). Database client programs and CLI utilities are diverse, so you can install and use the tool that best suits your needs.
5-1. ### Connecting to Bastion host
- In the Windows environment of the PC that will connect to the Bastion host, run Remote Desktop Connection, then enter the NAT IP of the Bastion Host and click the Connect button.
- When the remote desktop connection succeeds, user credential input window opens. 2. Enter the ID and Password verified in 2-3. Bastion host 접속 ID 및 PW 확인하기 and click the Confirm button.
5-2. ### Install the DB client program (SSMS) on the Bastion host
- Go to the official Microsoft SQL Server page and download the SSMS program.
- SSMS program download URL: https://learn.microsoft.com/en-us/ssms/download-sql-server-management-studio-ssms
- Connect the user’s PC hard drive to upload the file to the Bastion host.
- Click the Details button of the Local devices and resources item on the Local Resources tab of the Remote Desktop Connection.
- Select the local disk of the location where the file was downloaded on the drive, and click the Confirm button.
- Copy the downloaded file, upload it to the Bastion Host, and click the SSMS (Microsoft SQL Server Management Studio) installation file to install.
5-3. ### Connecting to the Database using the DB client program (SSMS)
- Run SSMS (Microsoft SQL Server Management Studio). 1. Connect to Server A popup window appears.
- In the Connect to Server popup, enter the Database server information created in 3-1. Microsoft SQL Server(DBaaS) 서비스 생성하기 and click the Connect button.
Required input element item input value Server type Database Engine Server name Database server IP, Database Port (ex. 192.168.10.1,2866) Authentication SQL Server Authentication Login Database username Password Database password Encryption Optional Table DB connection client program input fields - When the connection is complete, the Database will be accessed. 3. After connecting, you can perform simple queries, etc.
3 - API Reference
4 - CLI Reference
5 - Release Note
Microsoft SQL Server(DBaaS)
- Add secondary DR, AD integration, and immediate backup functionality
- You can configure a disaster recovery Secondary using the Secondary configuration (Other Region) feature.
- Supports integration with the user‑built Active Directory(AD) environment.
- If additional data protection is needed, you can quickly create a backup using the instant backup feature.
- ServiceWatch service integration
- You can view CPU, memory, and DB performance monitoring information through the ServiceWatch service.
- Add third-generation server type
- The third-generation server type has been newly added. * For more details, see Microsoft SQL Server(DBaaS) 서버 타입.
- Add Microsoft SQL Server (DBaaS) functionality
- 2nd-generation server type Add
- Add a 2nd‑generation (db2) server type based on the Intel 4th‑generation (Sapphire Rapids) Processor. * For more details, see Microsoft SQL Server(DBaaS) 서버 타입.
- DB User and Access Control Management Add
- For more details, refer to DB 사용자 관리, DB 접근 제어 관리
- DB Audit Log Export feature added
- For more details, see DB Log Export.
- Backup Notification Feature provided
- Provides notification functionality for backup success and failure. * For more details, refer to 알림 정책 생성하기.
- Add HDD, HDD_KMS type to the Block Storage type
- 2nd-generation server type Add
- A Microsoft SQL Server (DBaaS) service that enables easy creation and management of Microsoft SQL Server in a web environment has been launched.
