Vitor Fava Lets go faster on Azure SQL

Vitor Fava Let’s go faster on Azure SQL Database using Hyperscale service tier

Agenda • A brief history about the SQL Database? • What are the service models available? • Tell more about the Hyperscale, please?

About me • Pass Chapter Leader do SQLManiacs • Vitor. fava@vitadbsolutions. com • http: //vfava. wordpress. com • http: //www. youtube. com/vitortff • https: //groups. google. com/group/sqlmaniacs Vitor Fava • Tele. Gram Principal Database Architect – Vita Database Solutions vitortadeu. fava @sqlservermaniac /vitorfava GROUP LEADER SQLSATURDAY ORGANIZER

A brief history about the SQL Database • Relational database service in the cloud based on the Microsoft SQL Server engine; • Focus on rapid app development and accelerating your time to market, rather than managing virtual machines and infrastructure; • SQL Database supports existing SQL Server tools, libraries and APIs;

What are the service models available? • DTU • Provides bundled compute and storage packages balanced for common workloads; • Best for customers who want simple, preconfigured resource options; • v. Core • Provides a choice between a provisioned compute tier and a serverless (preview) compute tier; • You can also automatically pause and resume the databased on workload activity; • Best for customers who value flexibility, control, and transparency;

What are the service models available?

Tell more about the Hyperscale, please? • The Hyperscale service tier in Azure SQL Database is the newest service tier in the v. Core-based purchasing model; • Highly scalable storage and compute performance tier; • Leverages the Azure architecture to scale out the storage and compute resources for an Azure SQL Database;

Tell more about the Hyperscale, please? • Support for up to 100 TB of database size; • Nearly instantaneous database backups; • Fast database restores;

Tell more about the Hyperscale, please? • Higher overall performance due to higher log throughput and faster transaction commit times regardless of data volumes; • Rapid scale out - you can provision one or more read-only nodes for offloading your read workload and for use as hot-standbys; • Rapid Scale up - you can, in constant time, scale up your compute resources to accommodate heavy workloads;

Hyperscale Architecture

Who should consider the Hyperscale service tier? • Customers who have large On-Premisse databases who are already in the cloud and are limited by the maximum database size restrictions (1 -4 TB); • Customers who seek high performance and high scalability for storage and compute; • Customer with a highly OLTP workload;

BE THE MASTER OF YOUR CAREER