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 automates Microsoft SQL Server installation and offers 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 a desired point in time.

Provided features

Microsoft SQL Server (DBaaS) provides the following features.

• Auto Provisioning: UI allows installation and configuration of Database(DB), and provides a Primary-Secondary redundancy configuration based on Always On. When the Primary server fails, it automatically fails over to the Secondary.
• Operation Control Management: Provides functionality to control the state of running servers. In addition to start and stop, restart is possible when there is a DB issue or to apply configuration changes. When configured for high availability (HA), users can manually perform node switching between Primary and Secondary via a switch‑over.
• Backup and Recovery: Provides data backup functionality based on its own backup commands. Users can set the backup time window, retention organization, and Full backup day, and additional fees apply based on backup volume. It also offers a recovery function for backed‑up data, creating a separate DB when the user performs a recovery and restoring to the point in time selected by the user (backup save point, custom point). When restoring to a user‑specified point, the restore time can be set to 5 minutes/10 minutes/30 minutes/1 hour before the stored backup file and archive file.
• Version Management: Provides version upgrade (Minor) functionality for certain feature improvements and security patches. Users can choose whether to perform a backup for the version upgrade, and if a backup is performed, data is backed up before applying the patch, then the DB engine is updated.
• Secondary configuration: You can add a read‑only Read Replica (Secondary Replica), which expands read performance and distributes load.
• Audit Settings: Provides an audit configuration feature that can monitor users’ DB access and the results of DDL (Data Definition Language)/DML (Data Manipulation Language) operations.
• Parameter management: Modification of DB configuration parameters related to performance improvement and security is possible.
• Service Status Query: Retrieves the latest status of the current DB service.
• Monitoring: CPU, memory, DB performance monitoring information can be viewed through the Cloud Monitoring service.
• DB User Management: View and manage DB account (user) information registered in the DB.
• Export DB Log: You can export stored logs to the user’s Object Storage through Audit settings.

Component

Microsoft SQL Server(DBaaS) provides pre-validated engine versions and various server types. Users can select and use them according to 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 can be used 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.

Because the supplier’s policy may cause the EOS and EoTS dates to change, 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

Server type

The server types supported by Microsoft SQL Server (DBaaS) are as follows.

For detailed information about the server types offered by Microsoft SQL Server (DBaaS), refer to Microsoft SQL Server(DBaaS) Server Types.

Standard db1v2m4

Preliminary Service

This is a list of services that must be pre-configured before creating the service. Please refer to the guide provided for each service and prepare in advance.