azure architect renew

Question

azure architect renew

Nguyen Dinh Phuong (DPS.FMS) 521

Your transactional database requirements exceed the maximum capacity of a single Azure SQL database in the General Purpose sevice tier. What should you implement to resolve the capacity issue ?

Sharding
Elastic pools
read scale-out

John Hoy 45 Reputation points

2023-12-13T09:54:44.7233333+00:00
Bullet point 2 is what you are looking for.

Sharding

Sharding is a technique to distribute large amounts of identically structured data across a number of independent databases. It is especially popular with cloud developers creating Software as a Service (SAAS) offerings for end customers or businesses. These end customers are often referred to as "tenants". Sharding may be required for any number of reasons:

The total amount of data is too large to fit within the constraints of an individual database

The transaction throughput of the overall workload exceeds the capabilities of an individual database

Tenants may require physical isolation from each other, so separate databases are needed for each tenant

Different sections of a database may need to reside in different geographies for compliance, performance, or geopolitical reasons.

https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-scale-introduction?view=azuresql#sharding

Answer accepted by question author

2 additional answers

Your answer

John Hoy 45 Reputation points

2023-12-13T09:54:44.7233333+00:00

Bullet point 2 is what you are looking for.

Sharding

Sharding is a technique to distribute large amounts of identically structured data across a number of independent databases. It is especially popular with cloud developers creating Software as a Service (SAAS) offerings for end customers or businesses. These end customers are often referred to as "tenants". Sharding may be required for any number of reasons:

The total amount of data is too large to fit within the constraints of an individual database

The transaction throughput of the overall workload exceeds the capabilities of an individual database

Tenants may require physical isolation from each other, so separate databases are needed for each tenant

Different sections of a database may need to reside in different geographies for compliance, performance, or geopolitical reasons.

https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-scale-introduction?view=azuresql#sharding

Answer 1

Alberto Morillo 35,501 MVP Volunteer Moderator

I would choose sharding to easily scale out databases.

Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases, but no only one database.

Read scale out will help you redirect read workloads to replicas only.

luigi girgenti 1 Reputation point

2022-11-03T14:47:08.143+00:00

siamo sicuri?
KurtBMayer 841 Reputation points

2023-02-21T22:52:44.79+00:00

Further, "Read scale-out cannot be enabled in Basic, Standard, or General Purpose service tiers."

https://learn.microsoft.com/en-us/azure/azure-sql/database/read-scale-out?view=azuresql#enable-and-disable-read-scale-out-for-sql-database
Francisco Ferreira 25 Reputation points

2023-03-17T00:53:40.08+00:00

Sharding is to break your data into different sets that can then be processed by different databases.
Not all datasets are suitable for this operation, and nothing in the question hints that it is.

Elastic pools, on the other hand, allow you to provision a certain maximum amount of database resources (storage, engines, etc), which can then be used by any number of databases, including a single one.

I went for Elastic pools in this one and got 88% on my renewal. Cant be a 100% sure of my answers because I did not pay attention to the score of this specific session at end.

Answer 2

Nguyen Dinh Phuong (DPS.FMS) 521

thank you for your support

Alberto Morillo 35,501 Reputation points MVP Volunteer Moderator

2022-06-28T03:56:02.073+00:00

Good luck. Best wishes.

Answer 3

Sharding

Sharding is a technique to distribute large amounts of identically structured data across a number of independent databases. It is especially popular with cloud developers creating Software as a Service (SAAS) offerings for end customers or businesses. These end customers are often referred to as "tenants". Sharding may be required for any number of reasons:

The total amount of data is too large to fit within the constraints of an individual database
The transaction throughput of the overall workload exceeds the capabilities of an individual database
Tenants may require physical isolation from each other, so separate databases are needed for each tenant
Different sections of a database may need to reside in different geographies for compliance, performance, or geopolitical reasons.

https://learn.microsoft.com/en-us/azure/azure-sql/database/elastic-scale-introduction?view=azuresql#sharding

Share via

azure architect renew

2 additional answers

Your answer