SQL Server Azure Hyperscale: Setup

With the assistance of Skynats' server management services, let's examine the SQL server Azure hyperscale in more detail.

What is Hyperscale in Azure SQL?

The newest service tier in the vCore-based purchasing paradigm is the Hyperscale service tier in Azure SQL Database.

The storage and compute resources for an Azure SQL Database can be stretched out significantly beyond the limitations of the General Purpose and Business Critical service tiers using this service tier, which is highly scalable storage and compute performance tier.

The capabilities of Hyperscale

The following features are added by the Hyperscale service tier in Azure SQL Database:

• Databases with a maximum size of 100 TB are supported.

• Fast database backups of any size with no IO load on the CPU (based on file snapshots saved in Azure Blob storage).

• Based on file snapshots, databases can be restored in minutes as opposed to hours or days (not the size of data operation).

• Regardless of data volume, improved overall performance as a result of higher transaction log throughput and quicker transaction commit times

• Rapid scale out - To offload your read workload and serve as hot backups, we can provision one or more read-only replicas.

• Quick Scale Up - When dealing with heavy workloads, we can scale up your computational resources in real-time and then scale them back down when no longer required.

• Many of the practical limitations that have historically existed in cloud databases are eliminated by the Hyperscale service tier in Azure SQL.

The Hyperscale service tier has no database restrictions. Its adaptable storage architecture enables storage to grow as needed.

There is no predetermined upper limit for hyperscale databases. By providing additional replicas as needed for reading workload offloading, the Hyperscale service layer enables quick scale-out for workloads that require a lot of reading.

Additionally, the amount of time needed to create database backups or scale up or down is no longer directly related to the database's amount of data.

Hyperscale databases can almost instantly be backed up. We can also quickly scale up or down tens of terabytes of databases. We no longer worry about being constrained by the default configuration options thanks to this functionality.

Why take into account the Hyperscale service tier?

Customers who need increased performance and availability, quick backup and restore, and/or storage and compute scalability should choose the Hyperscale service tier.

Included are users who are migrating to the cloud to modernize their applications, as well as users who are already utilizing other service tiers in Azure SQL Database.

From OLTP to analytics, the Hyperscale service tier can handle a variety of database workloads. It is intended for workloads involving both OLTP and HTAP (hybrid transaction and analytical processing).

How can a database be moved to the Hyperscale service tier?

Before moving an existing Azure SQL Database database to the Hyperscale service tier, ascertain the goal service objective.

In many cases, we can choose a service target with the same hardware generation and vCores as the original database. If changes are required, we can do so later and with little disruption.

To migrate the database, select the appropriate tab from the Portal, Azure CLI, PowerShell, or Transact-SQL menus.

The Azure portal enables migration to the Hyperscale service tier by altering the database's pricing tier.

Configuration

Follow the instructions below to configure SQL Server hyperscale directly.

1. First, select the database you want to migrate in the Azure interface.

2. Choose Compute + storage from the left navigation bar after that.

3. Thirdly, make use of the Service tier drop-down menu to expand the service tier options.

4. Choose Hyperscale from the selection menu (On-demand scalable storage).

5. Examine the Hardware Configuration after that. If necessary, modify the configuration to choose the best hardware setup for the workload.

6. Look at the option for saving money. Check this box if we want to use Azure Hybrid Benefit for this database and are eligible for it.

7. The vCores slider can be used to change the number of vCores that are available for our database under the Hyperscale service tier.

8. The High-AvailabilitySecondaryReplicas slider can then be used to change the number of replicas under the Hyperscale service tier.

9. To confirm and apply the configurations, select the Apply button.

We can keep an eye on a Hyperscale database's operations as they are happening.