Search Azure terms

Databases premium PostgreSQL high availability PostgreSQL high availability means Azure keeps a standby flexible server ready so the database can continue after certain failures or planned failover events. Instead of relying on one server instance, the primary and standby are kept in sync. Depending on the design, the standby can be in the same availability zone or a different zone. This reduces downtime risk, but it does not remove every responsibility. Applications still need retry logic, connection handling, monitoring, tested failover procedures, and a cost owner because high availability adds real infrastructure. PostgreSQL flexible server intermediate 6 commands Aliases: PostgreSQL high availability, postgresql high availability, Azure Database for PostgreSQL flexible server Quick peek Open full term page

Databases premium MySQL high availability MySQL high availability means a MySQL Flexible Server configuration that keeps standby capacity available to reduce downtime during maintenance or failures. You see it when teams protect production databases for commerce, healthcare, finance, SaaS, and internal systems from planned or unexpected outages. Think of it as database resilience built into the server, not a complete disaster-recovery plan. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium Eventual consistency Eventual consistency is the weakest Azure Cosmos DB consistency level, where reads can return a subset of writes and all writes become available eventually. Teams use it to favor low-latency, high-availability reads for workloads that can tolerate temporarily stale or out-of-order data. It is not strong consistency, session consistency, a conflict-resolution strategy, a cache setting, or permission to ignore user-facing correctness requirements. In production, confirm account consistency setting, client overrides, read region, write region, session tokens, replication latency, stale-read tolerance, conflict policy, and application workflows that read after writes before treating the design as healthy or ready for release. Azure Cosmos DB intermediate 6 commands Aliases: eventual consistency level, Cosmos DB eventual consistency, eventually consistent reads Quick peek Open full term page

Databases premium Flexible server A flexible server is the Azure Database deployment model for managed PostgreSQL or MySQL servers with configurable compute, storage, availability, maintenance, backup, and networking options. Teams use it to host managed relational databases with more control over maintenance windows, compute tiers, backup retention, high availability, private networking, stop-start behavior, and performance settings. It is not a self-managed VM database, a single-server compatibility promise, a free unlimited database tier, or proof that schema design, indexes, failover, and application connection pooling are correct. Azure managed databases intermediate 6 commands Aliases: Azure Database flexible server, PostgreSQL flexible server, MySQL flexible server, managed flexible database server Quick peek Open full term page

Databases premium PostgreSQL flexible server The managed Azure PostgreSQL server resource that owns compute, storage, backups, networking, high availability, parameters, and databases. PostgreSQL flexible server fundamentals 6 commands Aliases: PostgreSQL flexible server, postgresql flexible server, Azure Database for PostgreSQL flexible server, managed PostgreSQL, backup retention, high availability, private access Quick peek Open full term page

Databases premium Azure Database for MySQL Flexible Server A fully managed Azure database service for MySQL workloads with configurable compute, storage, backups, networking, maintenance, and high availability options. Managed MySQL intermediate 5 commands Aliases: MySQL Flexible Server Quick peek Open full term page

Databases premium Azure Database for PostgreSQL Flexible Server A fully managed Azure PostgreSQL service with configurable compute, storage, backups, networking, maintenance, extensions, and high availability options. Managed PostgreSQL intermediate 5 commands Aliases: PostgreSQL Flexible Server Quick peek Open full term page

Databases premium Azure SQL Business Critical tier Azure SQL Business Critical tier is a vCore service tier for OLTP workloads that need high transaction rates, low-latency I/O, and high resilience through isolated replicas. Azure SQL Database fundamentals 5 commands Aliases: Azure SQL Business Critical tier, Business Critical tier, BusinessCritical, Premium-like vCore tier, SQL Business Critical Quick peek Open full term page

Databases premium PostgreSQL PostgreSQL is an open-source relational database engine. In Azure, Azure Database for PostgreSQL provides a managed Flexible Server service with compute, storage, backup, security, networking, monitoring, and high-availability capabilities for application and analytical workloads. across development, production, and migration scenarios. Database advanced 5 commands Aliases: Azure Database for PostgreSQL, Azure PostgreSQL, PostgreSQL flexible server, managed PostgreSQL Quick peek Open full term page

Databases premium PostgreSQL backup retention Azure Database for PostgreSQL automatically backs up flexible servers and retains the files and transaction logs for a configured window. The retention period defines how far back point-in-time restore can recover, with seven days as the default and up to thirty-five days configurable. PostgreSQL flexible server fundamentals 5 commands Aliases: Azure PostgreSQL backup retention, Flexible Server backup retention, PostgreSQL PITR retention Quick peek Open full term page

Databases premium PostgreSQL general purpose compute PostgreSQL General Purpose compute is the middle production tier for Azure Database for PostgreSQL flexible server. It is meant for workloads that need steadier CPU and memory than Burstable, but do not need the higher memory profile of Memory Optimized. Teams use it when a database serves real users, background jobs, APIs, or reporting workloads with predictable demand. The choice affects cost, concurrency, high availability eligibility, and scaling options. It is not a magic performance setting; it is a capacity tier that still needs good indexes, query design, connection pooling, and monitoring. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL general purpose compute, postgresql general purpose compute, Azure Database for PostgreSQL flexible server Quick peek Open full term page

Databases premium Azure Cosmos DB Azure Cosmos DB is a fully managed database service for NoSQL, relational, and vector workloads. It supports global distribution, elastic scale, multiple APIs, request-unit capacity, backup, and high availability so modern applications can store and query data without operating database servers. Azure Cosmos DB fundamentals 4 commands Aliases: Azure Cosmos DB, Cosmos DB, Azure Cosmos DB for NoSQL, Cosmos database, global NoSQL database, request-unit database Quick peek Open full term page

Databases premium Geo-replication Geo-replication is a database disaster recovery pattern where data from a primary database is replicated to one or more secondary databases in other regions. Teams use it to keep a recoverable copy of important data, support read-locality scenarios, and prepare for manual or application-driven failover during a regional outage. In daily Azure work, it shows up when engineers configure Azure SQL active geo-replication, review failover plans, test secondary connectivity, compare it with failover groups, or investigate replication lag. High availability intermediate 4 commands Aliases: active geo-replication, database geo-replication, regional database replication Quick peek Open full term page

Storage premium GZRS redundancy GZRS redundancy is an Azure Storage replication option that synchronously replicates data across availability zones in the primary region and asynchronously replicates it to a secondary region. Storage accounts intermediate 4 commands Aliases: geo-zone-redundant storage, Standard_GZRS, GZRS Quick peek Open full term page

Databases premium Hyperscale Hyperscale is an Azure SQL Database service tier built for large databases, fast scale, high availability, and separated compute and storage architecture. Azure SQL intermediate 4 commands Aliases: Azure SQL Hyperscale, hyperscale, Hyperscale, Hyperscale service tier Quick peek Open full term page

Databases premium MySQL backup retention MySQL backup retention means the configured recovery window for automated backups on Azure Database for MySQL Flexible Server. You see it when teams decide how long production database backups must remain available for restore, compliance, and incident response. Think of it as a recovery promise measured in days, not a paperwork checkbox. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. MySQL flexible server fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL business critical compute MySQL business critical compute means a higher-performance MySQL Flexible Server compute choice for sustained production workloads that need stronger capacity and headroom. You see it when teams support payment, commerce, SaaS, analytics, or other databases with predictable high concurrency and business deadlines. Think of it as premium database capacity selected from measured demand, not from fear or guesswork. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. MySQL flexible server fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL flexible server parameter MySQL Flexible Server parameter means a configurable server setting that changes MySQL behavior on Azure Database for MySQL Flexible Server. You see it when teams tune connections, TLS behavior, character sets, memory-related settings, timeouts, logging, or workload-specific database behavior. Think of it as a live behavior control that should be changed from evidence, not copied blindly from a tuning guide. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. MySQL flexible server intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL general purpose compute MySQL general purpose compute means the balanced MySQL Flexible Server compute tier for steady production workloads that need predictable capacity without premium cost. You see it when teams run customer applications, internal services, reporting databases, and line-of-business systems with regular demand. Think of it as balanced production capacity that should be sized from metrics. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL maintenance window MySQL maintenance window means the scheduled period when Azure may apply planned maintenance to a MySQL Flexible Server. You see it when teams align database maintenance with application traffic patterns, release freezes, support coverage, and business calendars. Think of it as a planned platform-change window, not a guarantee that applications need no resilience. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL read replica MySQL read replica means a secondary MySQL Flexible Server that asynchronously replicates data for read scaling or regional read placement. You see it when teams offload reporting, support read-heavy applications, reduce primary load, or place reads closer to users. Think of it as a read-scaling copy, not a synchronous high-availability replacement. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL same-zone HA MySQL same-zone HA means a MySQL Flexible Server high-availability option that keeps standby capacity in the same availability zone or local zone scope. You see it when teams want reduced downtime with lower zone-distance latency than a zone-redundant design may introduce. Think of it as local standby protection, not cross-zone resilience. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL server MySQL server means the Azure Database for MySQL Flexible Server resource that hosts databases and controls compute, storage, networking, backups, and maintenance. You see it when teams operate MySQL applications, manage database access, scale resources, configure networking, or recover data. Think of it as the managed server boundary around one or more MySQL databases. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL server compute tier MySQL server compute tier means the capacity family that determines the compute and memory shape for an Azure Database for MySQL server. You see it when teams size production databases, development systems, migrations, reporting workloads, and seasonal applications. Think of it as a capacity and cost decision that should match measured workload demand. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL storage autogrow MySQL storage autogrow means a MySQL Flexible Server setting that automatically increases storage when used capacity approaches the configured limit. You see it when teams protect databases from running out of storage during growth, imports, reporting, migrations, or seasonal demand. Think of it as automatic storage expansion, not automatic cost or performance optimization. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL advanced 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium MySQL zone-redundant HA MySQL zone-redundant HA means a MySQL Flexible Server high-availability option that places standby capacity in another availability zone for stronger zonal resilience. You see it when teams protect production databases from zone-level failures while accepting the design and latency tradeoffs. Think of it as cross-zone server resilience, not a full multi-region disaster-recovery plan. It matters because the setting changes how teams design, secure, operate, and troubleshoot the workload. Before changing it in production, know the owner, dependency, evidence, expected result, and rollback path. Azure Database for MySQL fundamentals 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases field-manual-complete MySQL flexible server MySQL flexible server is Azure Database for MySQL Flexible Server, a managed MySQL service with configurable compute, storage, backups, networking, high availability, maintenance, and server parameters. Microsoft Learn positions it as a production-ready database platform that reduces infrastructure work while preserving operational control. MySQL flexible server fundamentals 8 commands Aliases: No aliases yet Quick peek Open full term page

Databases field-manual-complete PostgreSQL major version upgrade A PostgreSQL major version upgrade moves a flexible server from one big PostgreSQL release to another, such as PostgreSQL 13 to 16. It is not the same as a minor patch. Major versions can change engine behavior, extension compatibility, role behavior, query plans, and application assumptions. Azure can perform an in-place upgrade, but it still requires planning, prechecks, storage headroom, a tested restore point, and clear downtime expectations. A successful upgrade cannot simply be rolled back, so teams should test on a restored copy before touching production. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL major upgrade, PostgreSQL flexible server upgrade, major version upgrade Quick peek Open full term page

Databases field-manual-complete PostgreSQL memory optimized compute PostgreSQL Memory Optimized compute is the tier you choose when the database needs more memory per CPU than a normal balanced server provides. It is often used for busy transactional systems, analytical queries, large working sets, connection-heavy applications, and workloads where caching more data in memory reduces disk pressure. It is not a magic performance switch. Teams still need good indexing, query design, storage sizing, and monitoring. The tier costs more than smaller options, so it should be chosen because evidence shows memory is the limiting factor. PostgreSQL flexible server fundamentals 5 commands Aliases: Memory Optimized PostgreSQL, PostgreSQL memory optimized tier, E-series PostgreSQL compute Quick peek Open full term page

Databases field-manual-complete PostgreSQL point-in-time restore PostgreSQL point-in-time restore means bringing a flexible server back to what it looked like at a specific earlier time, but Azure does this by creating a new server. It is used after accidental deletes, bad deployments, data corruption, or to clone production for validation. The restore must be inside the server’s backup retention period. It is not a single-table undo button and it does not overwrite production. After the new server exists, teams compare data, redirect applications, export recovered rows, or keep it for testing. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL PITR, PostgreSQL restore point, flexible server point-in-time restore Quick peek Open full term page

Databases field-manual-complete PostgreSQL same-zone HA PostgreSQL same-zone HA means Azure keeps a standby flexible server replica in the same availability zone as the primary server. If the primary server has a node or server-level failure while the zone remains healthy, Azure can fail over to the standby. It is high availability, but not full zone redundancy. The standby is not a read replica for reporting. Think of it as a local safety partner for the primary database when cross-zone placement is unavailable, too costly, or not the right latency tradeoff. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL zonal HA, Same-zone high availability, Zonal high availability for PostgreSQL, PostgreSQL HA standby in same zone Quick peek Open full term page

Databases field-manual-complete PostgreSQL server compute tier A PostgreSQL server compute tier is the performance-and-cost lane you choose for an Azure Database for PostgreSQL flexible server. Burstable is for small or variable workloads, General Purpose is the common production middle ground, and Memory Optimized is for workloads that need more memory per vCore. The tier is not just a label. It affects how much CPU and memory the database can use, whether high availability is available, how... PostgreSQL flexible server fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases field-manual-complete PostgreSQL standby zone A PostgreSQL standby zone tells you where the standby high-availability replica lives relative to the primary PostgreSQL flexible server. If the standby is in a different availability zone, the design can keep the database available through many zone-level failures. If it is in the same zone, it can still protect against server-level failure, but it does not protect against the whole zone going down. This setting is not a read-replica... Data platform intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases field-manual-complete PostgreSQL zone-redundant HA PostgreSQL zone-redundant HA is the high-availability choice that places the primary PostgreSQL flexible server and its standby in different availability zones. If the primary server or its zone has a problem, Azure can fail over to the standby. The application still connects through the server endpoint, but the database platform has a second copy in another zone ready to take over. This is a production resilience feature, not a performance scale-out feature, because the standby does not serve normal read traffic. PostgreSQL flexible server fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases verified Redis Enterprise cache A Redis Enterprise cache is an Azure cache instance running on Redis Enterprise rather than basic open-source Redis nodes. In Azure Cache for Redis Enterprise tiers, it provides clustered data nodes, quorum behavior, Enterprise/Enterprise Flash SKUs, modules, persistence, and active geo-replication for demanding workloads. Azure Managed Redis intermediate 5 commands Aliases: Azure Cache for Redis Enterprise, Enterprise Redis cache, Enterprise cache Quick peek Open full term page

Databases field-manual-complete Redis persistence Redis persistence is the option that lets a Redis cache survive more than memory loss. Normal Redis is often treated as disposable because data lives in memory and can be rebuilt from a database. Persistence changes that assumption by saving snapshots or append-only changes so the cache can be restored after a serious failure. In Azure, it belongs with workload recovery planning, not routine backup exports. You still decide which data is safe to keep in Redis and which must remain in a durable database. Cache and in-memory data fundamentals 5 commands Aliases: Redis data persistence, RDB persistence, AOF persistence, Redis persisted cache Quick peek Open full term page

Databases complete Single database A fully managed Azure SQL Database with its own compute, storage, backup, and service-tier settings under a logical server. Azure SQL fundamentals 5 commands Aliases: Azure SQL single database, SQL single database, single Azure SQL database Quick peek Open full term page

Databases complete SQL database export Microsoft Learn describes SQL database export as creating a BACPAC file that contains database schema and data and storing it in Azure Storage or local tooling output. Export can be started from the portal, PowerShell, Azure CLI, SqlPackage, SSMS, or supported developer tools. Azure SQL fundamentals 5 commands Aliases: database export, Azure SQL BACPAC export, SQL export, export database to BACPAC Quick peek Open full term page

Databases complete SQL Managed Instance Microsoft Learn describes Azure SQL Managed Instance as a fully managed PaaS database engine with near complete SQL Server compatibility, native virtual network deployment, automated patching and backups, and instance-scoped features that help teams lift and shift SQL Server workloads with fewer application or database changes. Azure SQL fundamentals 5 commands Aliases: SQL MI, Azure SQL MI, Azure SQL Managed Instance, managed SQL instance Quick peek Open full term page

Databases complete SQL Managed Instance service tier Microsoft Learn describes SQL Managed Instance service tiers as purchasing-model choices, such as General Purpose, Next-gen General Purpose, and Business Critical, that define architecture, storage limits, availability behavior, performance characteristics, and billing for a managed instance. Review it using workload evidence. for production database workloads. SQL Managed Instance intermediate 5 commands Aliases: SQL MI service tier, Azure SQL MI tier, managed instance tier, SQL Managed Instance SKU tier Quick peek Open full term page

Databases complete SQL managed instance zone redundancy Microsoft Learn describes SQL Managed Instance zone redundancy as a high-availability configuration that spreads managed instance components across Azure availability zones in supported regions. It improves protection from datacenter-level failures while preserving the managed instance endpoint and using Azure SQL platform redundancy rather than application-managed failover. SQL Managed Instance intermediate 5 commands Aliases: SQL MI zone redundancy, Azure SQL Managed Instance zone redundancy, zone redundant managed instance Quick peek Open full term page

Databases complete SQL zone redundancy Microsoft Learn describes SQL zone redundancy as an Azure SQL high-availability option that places database replicas across availability zones within a supported region. It improves resilience to a zone-level failure while keeping the database in the same region and service boundary. Azure SQL availability intermediate 5 commands Aliases: Azure SQL zone redundancy, zone-redundant SQL Database, SQL availability zones, zone redundant database Quick peek Open full term page

Databases verified Redis cache SKU A Redis cache SKU is the size and capability package you buy for the cache. It answers questions like how much memory the cache has, what performance level it can provide, which high-availability or scaling features are available, and how much it will cost. For Azure teams, SKU is not just a billing label. It is a design decision that affects latency, resilience, migration options, monitoring expectations, and whether the cache can support the application when traffic grows. Cache and in-memory data fundamentals 4 commands Aliases: Redis SKU, cache SKU, Redis size Quick peek Open full term page

Databases verified Redis cache tier A Redis cache tier is the broad class of cache capability, while the SKU is the exact purchasable size inside that class. The tier tells you what kind of workload the cache is meant for: simple development, production high availability, larger scale, flash-backed capacity, or a managed enterprise-style Redis deployment. For learners, tier is the decision that says what features and operating expectations are on the table before anyone argues about the exact memory size. Cache intermediate 4 commands Aliases: Redis tier, cache tier, Redis performance tier Quick peek Open full term page

Databases field-manual-ready Multi-region writes Multi-region writes let Azure Cosmos DB applications write data in more than one region instead of one primary write region. Azure Cosmos DB advanced 4 commands Aliases: multiple write regions, active-active Cosmos DB, multi-region writes, Cosmos DB multi-write Quick peek Open full term page

Databases complete SQL Hyperscale named replica Microsoft Learn describes a Hyperscale named replica as a named, read-only replica of an Azure SQL Database Hyperscale database. It can be created with its own database name, compute size, and access boundary, then used for read scale-out, workload isolation, and resilient testing. Data platform intermediate 4 commands Aliases: Hyperscale named replica, Azure SQL named replica, named read replica, Hyperscale read replica Quick peek Open full term page

Monitoring and Observability premium Availability result Availability result is the recorded outcome of an Application Insights availability test run, including whether the probe succeeded, how long it took, and where it ran. In Azure, teams encounter it when teams query Azure Monitor Logs after a synthetic web test reports failures, slow responses, or regional differences. The useful question is what behavior Availability intermediate 4 commands Aliases: AppAvailabilityResults, availability test result, Application Insights availability result Quick peek Open full term page

Compute premium Availability set Availability set is a placement group for Azure virtual machines that spreads instances across separate fault and update domains inside one datacenter. In Azure, teams encounter it when architects deploy two or more classic VM instances for an application tier that still needs datacenter-level hardware separation. The useful question is what behavior it proves, who Availability fundamentals 4 commands Aliases: VM availability set, fault domain set, update domain set Quick peek Open full term page

Monitoring and Observability premium Availability test Availability test is an outside-in monitor that repeatedly calls a public HTTP or HTTPS endpoint and records whether it responded quickly enough. In Azure, teams encounter it when product teams need synthetic checks for websites, APIs, or critical external dependencies before users report an outage. The useful question is what behavior it proves, who owns Availability intermediate 4 commands Aliases: Application Insights availability test, web test, standard test, synthetic test Quick peek Open full term page

Compute premium Availability zone Availability zone is a physically separate zone inside an Azure region with independent datacenter infrastructure such as power, cooling, and networking. In Azure, teams encounter it when architects choose whether a workload should pin resources to one zone or spread service instances across multiple zones. The useful question is what behavior it proves, who owns Availability fundamentals 4 commands Aliases: Azure availability zone, zone, zone-redundant deployment, zonal deployment Quick peek Open full term page