Cloud DB for MSSQL resource management
- Print
- PDF
Cloud DB for MSSQL resource management
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
Check the resource information of Cloud DB for MSSQL. All activities that you can perform in Cloud DB for MSSQL are mapped with the resource type and task history by resource type (action) defined in Resource Manager. Based on the value mapped, the task history actually performed by users is collected in Cloud Activity Tracer, and the admin can use it when monitoring the users' activities or creating audit reports. In addition, the resource type is used as a standard for usage permissions by user in Sub Account.
The following describes the resource and task history by resource type:
- Resource
- Unit of key information managed by each service
- Object that can be created, changed, and deleted by the user
- Unique value by each service of NAVER Cloud Platform
- Task history by resource type (action)
- History of tasks performed by the user through the console and API
- Act of creating, changing, or deleting resources
The following describes Cloud DB for MSSQL's resource type and task history information by resource type:
| Service name (product code) | Resource type | Task history by resource type |
|---|---|---|
| Cloud DB for MSSQL(CloudDBforMSSQL) | ConfigGroup | Change Config Group Value |
| Create Config Group | ||
| Delete Config Group | ||
| Service | Change Service Name | |
| Change server spec | ||
| Change to high availability | ||
| Create DB server | ||
| Create Standby Master Server | ||
| Create Standby Master Server With Failover | ||
| Create recovery server | ||
| Delete DB server | ||
| Cloud DB for MSSQL(VPCCloudDBforMSSQL) | ConfigGroup | Change Config Group Value |
| Create Config Group | ||
| Delete Config Group | ||
| Server | Adjust Read Time | |
| Attach Public Domain To Server | ||
| Change Data Storage Size | ||
| Change Server Spec | ||
| Change Server To High Availability | ||
| Change Server To Stand Alone | ||
| Create DB Server | ||
| Create DB Server Due to Restoration | ||
| DB Server Failover | ||
| Delete DB Server | ||
| Detach Public Domain To Server | ||
| Export DB Log to Object Storage | ||
| Restart DB Server | ||
| Switch to Mirror DB Server Due to Failover | ||
| Switch to Principal DB Server Due to Failover | ||
| Service | Add Slave Server To Service | |
| Change Backup Setting | ||
| Change Config Group | ||
| Change Config Group Value in Cluster | ||
| Change DB Service Spec | ||
| Change Service Name | ||
| Change Service To High Availability | ||
| Change Service To Stand Alone | ||
| Configure AuditLog | ||
| Create Cloud DB Service | ||
| DB Service Auto Failover | ||
| Delete Cloud DB Service | ||
| Delete Slave Server From Service | ||
| Export Backup To Object Storage | ||
| Restart DB Service With Failover | ||
| Restore Backup to Create New Service | ||
| Upgrade Cloud DB Service |
Note
- Resource Manager: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Resource Manager user guide.
- Cloud Activity Tracer: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Cloud Activity Tracer user guide.
- Sub Account: it is a service provided by NAVER Cloud Platform for free. The permissions are designed based on the resource type defined in Resource Manager. However, because the resource type group and the action by resource type are configured in Sub Account, they differ from the group and action values defined in Resource Manager.
Was this article helpful?