The main differences between vCore and DTU relate to how computing resources are provisioned and billed in Azure Database Service services. Let's detail each one:
Virtual Core
- Purchase Model The vCore (Virtual Core) model is a virtual core-based model that provides flexibility to scale computing resources and memory independently.
- Setup Allows users to choose the amount of CPU, memory and IOPS (Input/Output Operations Per Second) they need. This provides greater control over resources and cost optimization.
- Types of Service
- Levels There are three main ones: General Purpose, Business Critical and Hyperscale, each suitable for different types of workloads.
- Licensing It can be based on Azure Hybrid Benefit, which allows cost savings if you already have SQL Server licenses with Software Assurance.
- Billing Based on virtual core (vCore) colors, memory usage, storage usage, and additional features such as backups and networking.
Database Transaction Unit
- Purchase Model DTU is a pre-configured package of resources that includes CPU, memory, data read and write capabilities.
- Configuration Resources are provisioned as a package, with predefined levels that offer a balanced combination of CPU, memory, and IOPS.
- Service Types :
- Service Levels Each one offering different capabilities and performance resources.
- Billing Based on the number of provisioned DTUs. The higher the level of DTU, the greater the computing power and IOPS capacity.
Detailed Comparison
Feature | Core | Technical University |
---|---|---|
Resource Control | Fine and Flexible | Balanced Package |
CPU Dimensions | Choice of Cores (CPU) | Pre-configured |
Memory | Independent Choice | Included in the DTU package |
Input/Output Operations Per Second | Adjustable | Included in the DTU package |
Service Levels | Broad, High-Stakes, Cloud-Scale | Three options: Basic, Standard, Premium |
Licensing | Azure Hybrid Benefit is available | Not applicable |
Billing | Based on vCores, memory, and IOPS | Based on the amount of provisioned DTUs |
When to wear each one:
core It's ideal if you need flexibility to adjust your computer resources and memory independently. It's also beneficial if you want to take advantage of your existing SQL Server licenses to save costs.
Technical University It's more suitable if you prefer a simplified approach where you don't need to worry about adjusting individually the CPU, memory, and IOPS, and instead prefers a pre-configured package of resources.
These options allow you to choose a model that best aligns with your specific performance and budget needs in Azure SQL Database.