Let us take a closer look at the SQL server azure hyperscale with the support of our Server management support services at Bobcares.

What is Hyperscale in Azure SQL?

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

This service tier is highly scalable storage and computes performance tier that uses the Azure architecture to stretch out the storage and compute resources for an Azure SQL Database far beyond the constraints of the General Purpose and Business Critical service tiers.

The capabilities of Hyperscale

The Hyperscale service tier in Azure SQL Database adds the following features:

• Databases of up to 100 TB in size are supported.
• Fast database backups of any size (based on file snapshots saved in Azure Blob storage) with no IO impact on CPU resources.
• Database restores in minutes rather than hours or days (based on file snapshots) (not a size of data operation).
• Greater overall performance as a result of increased transaction log throughput and faster transaction commit times regardless of data volume.
• Rapid scale out – we can provision one or more read-only replicas for offloading your read workload and for use as hot-standbys.
• Rapid Scale Up – We can scale up your computational resources in real time to suit heavy workloads, and then scale them back down when not needed.

The Hyperscale service tier in Azure SQL eliminates many of the practical constraints that have historically existed in cloud databases.

There are no limits on databases in the Hyperscale service tier. Storage expands as needed thanks to its adaptable storage architecture.

In truth, there is no set maximum size for Hyperscale databases. The Hyperscale service layer allows rapid scale-out for read-intensive workloads by providing extra replicas as needed for offloading read workloads.

Furthermore, the time it takes to produce database backups or scale up or down is no longer proportional to the volume of data in the database.

Hyperscale databases can be backed up almost instantly. We can also scale tens of terabyte databases up or down in minutes. This functionality alleviates our concerns about being limited by the original configuration choices.

Why consider the Hyperscale service tier?

The Hyperscale service tier is designed for customers who require enhanced performance and availability, as well as quick backup and restore and/or storage and compute scalability.

Users that are migrating to the cloud to modernize their applications are included, as are users who already use other service tiers in Azure SQL Database.

The Hyperscale service tier can handle a wide range of database workloads, from OLTP to analytics. It is designed for online transaction processing (OLTP) and hybrid transaction and analytical processing (HTAP) workloads.

How to migrate a database to the Hyperscale service tier?

Determine the goal service objective before migrating an existing database in Azure SQL Database to the Hyperscale service tier.

In many circumstances, we can select a service target with the same number of vCores and hardware generation as the original database. If necessary, we will be able to make changes later with minimum downtime.

Choose the appropriate tab from Portal, Azure CLI, PowerShell, or Transact-SQL to migrate the database.

By changing the pricing tier for the database, the Azure portal allows migrating to the Hyperscale service tier.

Configuration

To head-on with the configuration on SQL server Azure hyperscale follow the steps given below.

1. Firstly, In the Azure interface, navigate to any database to migrate.
2. After that, select Compute + storage from the left navigation bar.
3. Thirdly, to increase the service tier possibilities, use the Service tier drop-down menu.
4. From the selection option, select Hyperscale (On-demand scalable storage).
5. After that, examine the Hardware Configuration. Change configuration if desired to select the right hardware configuration for the workload.
6. Examine the Save money option. If we qualify for Azure Hybrid Benefit and want to use it for this database, check this box.
7. If we want to adjust the number of vCores accessible for our database under the Hyperscale service tier, we may use the vCores slider.
8. After that to adjust the number of replicas under the Hyperscale service tier, we can use the High-AvailabilitySecondaryReplicas slider.
9. Finally, Choose the Apply button to confirm and apply the configurations.

We can monitor operations for a Hyperscale database while the operation is ongoing.

[Need assistance with similar queries? We are here to help]

Conclusion

To conclude we have learned more about the SQL server azure hyperscale, its configurations on it, and how to migrate a database to the hyperscale service tier with the support of our Server management support services.