Yandex.Cloud
  • Services
  • Why Yandex.Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Yandex Managed Service for SQL Server™
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Information about existing clusters
    • Creating clusters
    • Connecting to databases
    • Stopping and starting clusters
    • Changing cluster and database settings
    • Managing SQL Server hosts
    • Managing databases
    • Managing users
    • Granting permissions and roles
    • Managing backups
    • Deleting clusters
  • Concepts
    • Relationship between service resources
    • Host classes
    • Networks in Managed Service for SQL Server
    • Quotas and limits
    • Storage types
    • Backups
  • Access management
  • Pricing policy
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • BackupService
      • ClusterService
      • DatabaseService
      • ResourcePresetService
      • UserService
      • OperationService
    • REST
      • Overview
      • Backup
        • Overview
        • get
        • list
      • Cluster
        • Overview
        • backup
        • create
        • delete
        • get
        • list
        • listBackups
        • listHosts
        • listLogs
        • listOperations
        • move
        • restore
        • start
        • stop
        • update
      • Database
        • Overview
        • create
        • delete
        • get
        • list
      • ResourcePreset
        • Overview
        • get
        • list
      • User
        • Overview
        • create
        • delete
        • get
        • grantPermission
        • list
        • revokePermission
        • update
      • Operation
        • Overview
        • get
  • Questions and answers
    • General questions
  1. Concepts
  2. Relationship between service resources

Relationship between service resources

    The main entity used in Managed Service for SQL Server is a database cluster.

    Each cluster consists of one or more database hosts, which are virtual machines with DBMS servers deployed on them. Cluster hosts may reside in different availability zones. More about the geo scope of Yandex.Cloud.

    • A cluster consisting of multiple hosts has automatic failover, because the hosts can take over each other's functions as the cluster's primary replica.

    • A single-host cluster is cheaper, but it doesn't guarantee fault tolerance.

    When creating a cluster, specify:

    • Host class: A VM template for deploying the cluster hosts. For a list of available host classes and their characteristics, see Host classes.

    • Environment: The environment where the cluster will be deployed:

      • PRODUCTION: For stable versions of your apps.
      • PRESTABLE: For testing, including the Managed Service for SQL Server service itself. The Prestable environment is first updated with new features, improvements, and bug fixes. However, not every update ensures backward compatibility.

    A database cluster created in a folder can be accessed by all VMs connected to the same cloud network. Learn more about networking.

    Alert

    The service can automatically access the system and diagnostic information of your databases to plot monitoring graphs and maintain the health of your cluster. The service never queries or uses the data that you saved to the database.

    Language
    Careers
    Privacy policy
    Terms of use
    © 2021 Yandex.Cloud LLC