6.3 Introduction to Azure SQL Databases

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

18 hours 58 minutes
Video Transcription
Welcome back on this episode, we're going to take a look at Azure sequel databases.
Our objectives include understanding what sequel day of a service is taking a look at our purchase models and some features and compliance options inside of the Azure sequel database service.
So chances are you've heard of Microsoft Sequel server before, But what offerings are available inside of Azure for sequel,
The Azure Sequel Databases, a relational database Manage service, You can create highly available and high performance data storage for applications and other solutions.
The service is based on the latest, stable version of the Microsoft sequel Server database engine. In fact, new capabilities are released to the sequel database service in Azure and then to sequel server itself without requiring any patching or upgrading.
When working with sequel in Azure as a past solution, there are a couple of different deployment models available. First, we have an option of a single database. This is a fully managed, an isolated database that can be used with modern applications or a micro service that needs a single, reliable source of data.
Next, we then have elastic pool where a bunch of single databases are grouped together and they share a set of resource is like CPU and memory. And then finally, for a pass solution we have managed instance, and this is a great option if you're migrating existing sequel databases from on Premises and Azure
as it's very compatible with on premises sequel server versions.
He uses the latest stable version of the sequel server features and is very similar to an instance of the Microsoft sequel server database engine.
And finally, we do have a non past solution where basically, you're deploying a virtual machine and installing sequel on top of it. You would use this option if you need operating system level access for your sequel server.
When purchasing sequel service is in Asher, we have to purchase models to choose from.
First is V Corps based. This allows for scaling your computer and storage resource is independently of each other.
Basically, you get more options on choosing the number of course and memory for serving the database
inside a V corps. There are three tiers of service we can choose from First, we have general purpose, hyper scale and business critical
general purpose balances between compute and stores options for budget oriented solutions,
while business critical is for applications that require high transaction rate and low I oh Leighton See
and hyper scale is for workloads, where you need to auto scale solutions for the storage size and the ability to scale vertically or horizontally,
and you can see how we can configure the different options inside of our tears here, based on the number of I ops or a late and see we need.
Our next purchase model option is DT. You based BTU based is a model that has a range of compute sizes that include a fixed amount of storage
retention periods for backups and a fixed price.
D T. U stands for database transaction units, which is a measure of CPU memory, reads and writes on our database storage
thes de to use our bundles of compute resources and storage that determined the database performance.
Using a D T model is simpler and has fixed payments per month.
In addition to regular D To use with a signed resource is that are always available to him. There's also elastic or e d. T. Use. This is where multiple databases might share. A pool of resource is and the solution might be more cost effective for databases that can consume a wide variety of resource is or have unpredictable usage patterns.
So at a given time, a database might be experiencing higher usage while another one is not so. The database with higher usage will use more. The resource is fromthe low usage data base.
We also have three tiers with the BTU based called Basic Standard and Premium. The primary differences between these tears is the maximum backup retention time CPU capacity, and I owe throughput.
When looking at a single database with R D. T. You limits, you can see we have basic standard premium.
And we have two characteristics that we can look at maximum storage size from two gigabytes all the way to four terabytes,
and then the maximum DT you units we have all the way from 5 to 4000.
Inside are elastic BTU limits. We still have the storage size per database
for elastic PTU limits. We have our three tiers again, and instead of just maximum storage, we have maximum storage size per database and then maximum storage size per pool. Then we also have the maximum e d. T. use per database and per pool, as well as the number of databases per pool
utilizing sequel Inside of Azure has
a couple of different features we would expect from Cloud Service is first. We have automatic backups with full differential and transaction log backups of sequel. We also have point in time restores which support recovery to any point in time. Within the automatic backup retention period,
we'll have active geo replication were single and pull. Databases can be configured for up to four readable secondary databases in the same or different azure regions. This allows you to enable your application that might have lots of read. Only transactions to use read only copies of the sequel database. In another data center
was lab auto fell over groups, which is just groups that enable high availability and load balancing at a global scale.
And then zone redundant data bases where you can provisioned databases across multiple availability zones within a region so you can have additional replicas for high availability and higher resilience.
As your sequel also comes with a variety of security and compliance features. First, we have data discovery and classification, which allows the service to discover classify label and protect your sensitive data inside the databases. We'll have
vulnerability assessments where you can discover in re mediate potential database problems to enhance your security.
Next, we have third detection, where you confined anomalous activity that might be harmful, such as attempts to excess or exploit the database. It could also provide recommended actions to take. Finally, we have data encryption in the last module we talked about sequel, Always Encrypted,
which allows for working with encrypted data that is in transit or being used by the application.
Azure sequel service is also used transparent data encryption or T d E for data at rest
that does it for some of our sequel service is Inside of Azure Coming up. Next, we're going to jump back to the portal and take a look at an azure sequel database demo. See you in the next episode.
Up Next