Search Azure terms

Databases field-manual-complete Npgsql Npgsql is the PostgreSQL driver that .NET applications commonly use to connect to Azure Database for PostgreSQL. The Azure database service hosts and manages the PostgreSQL server; Npgsql is the client-side library that opens connections, sends SQL, reads results, and works with Entity Framework providers. It is not a database server, Azure resource, or firewall rule. It is the bridge between C# code and PostgreSQL behavior, so configuration choices such as connection strings, TLS, pooling, timeouts, and authentication matter. PostgreSQL connectivity intermediate 4 commands Aliases: No aliases yet 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 command-rich Cosmos DB for PostgreSQL Azure Cosmos DB for PostgreSQL is a managed PostgreSQL service with Citus distributed tables, currently on a retirement path and not recommended for new projects. Data platform intermediate 4 commands Aliases: No aliases yet Quick peek Open full term page

Databases premium PostgreSQL connection string Application configuration that identifies the PostgreSQL server, database, port, authentication method, and TLS path used by a workload. Data platform intermediate 6 commands Aliases: PostgreSQL connection string, postgresql connection string, connection string, Azure Database for PostgreSQL connection string, FQDN, port 5432, port 6432 Quick peek Open full term page

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 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 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 burstable compute PostgreSQL burstable compute is the Burstable pricing tier for Azure Database for PostgreSQL flexible server. It uses B-series virtual machine sizes for workloads with modest average CPU demand that may need occasional bursts instead of continuously provisioned high performance. safely. PostgreSQL flexible server fundamentals 5 commands Aliases: Azure PostgreSQL B-series, Flexible Server burstable compute, PostgreSQL Burstable tier Quick peek Open full term page

Databases premium PostgreSQL connection pooling PostgreSQL connection pooling reuses database connections instead of opening a new server process for every request. Azure Database for PostgreSQL supports pooling strategies including built-in PgBouncer on supported flexible server tiers to reduce idle and short-lived connection overhead. across applications. PostgreSQL flexible server fundamentals 5 commands Aliases: Azure PostgreSQL PgBouncer, PgBouncer, PostgreSQL pooling, database connection pooling Quick peek Open full term page

Databases premium PostgreSQL database A named PostgreSQL catalog inside a flexible server that holds schemas, tables, extensions, permissions, and application data. Azure Database for PostgreSQL fundamentals 5 commands Aliases: PostgreSQL database, postgresql database, Azure Database for PostgreSQL database, database catalog, schema migration, charset, collation Quick peek Open full term page

Databases premium PostgreSQL extension An allowlisted PostgreSQL add-on package that expands database behavior, such as statistics, geospatial, vector, or cryptographic capability. PostgreSQL intermediate 5 commands Aliases: PostgreSQL extension, postgresql extension, Azure PostgreSQL extension, azure.extensions, CREATE EXTENSION, pgvector, pg_stat_statements Quick peek Open full term page

Databases premium PostgreSQL firewall rule A public-network access rule that permits a specific IPv4 range to reach an Azure Database for PostgreSQL flexible server. PostgreSQL flexible server intermediate 5 commands Aliases: PostgreSQL firewall rule, postgresql firewall rule, Azure PostgreSQL firewall, public access, IPv4 allowlist, source IP, start IP address Quick peek Open full term page

Databases premium PostgreSQL flexible server parameter A PostgreSQL flexible server parameter is a setting that changes how the managed PostgreSQL server behaves. Some parameters tune performance, such as memory, autovacuum, logging, query planning, connection handling, or extensions. Others control operational features such as audit logging, Query Store, PgBouncer, or required restart behavior. You do not sign in to the operating system and edit postgresql.conf; Azure exposes supported settings through the portal, CLI, REST, and ARM. Treat each parameter as a production change because one value can affect every database and application on the server. Data platform intermediate 5 commands Aliases: PostgreSQL flexible server parameter, postgresql flexible server parameter, Azure Database for PostgreSQL flexible server 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 PostgreSQL log analytics PostgreSQL log analytics means collecting PostgreSQL flexible server logs in Azure Monitor so operators can search them, build alerts, and investigate problems with KQL. Instead of downloading log files manually or guessing from symptoms, teams route PostgreSQLLogs and related categories to a Log Analytics workspace. The value comes from patterns: failed connections, slow queries, audit events, PgBouncer signals, configuration effects, and workload changes. It is not free and not automatically useful; teams must choose categories, retention, workspace access, alert logic, and dashboards that match the database risk. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL log analytics, postgresql log analytics, Azure Database for PostgreSQL flexible server Quick peek Open full term page

Databases premium PostgreSQL maintenance window A PostgreSQL maintenance window is the time Azure is allowed to perform scheduled platform maintenance for a flexible server. With a system-managed schedule, Azure chooses a suitable window. With a custom schedule, the team chooses the day and start time for the one-hour window. This matters because maintenance can involve updates that briefly affect availability or performance. The window is not a promise that nothing will ever happen outside it, but it gives teams a predictable place to plan patching communication, staffing, workload quiet periods, and post-maintenance checks. Azure Database for PostgreSQL intermediate 5 commands Aliases: PostgreSQL maintenance window, postgresql maintenance window, Azure Database for PostgreSQL flexible server Quick peek Open full term page

Databases field-manual-complete PostgreSQL stop/start PostgreSQL stop/start is the on-off control for an Azure Database for PostgreSQL flexible server. Stopping the server makes the database unavailable, so applications cannot connect or run queries until it is started again. It is useful when a lab, sandbox, migration rehearsal, or training environment does not need to run overnight. It is not a backup, deletion, failover, or pause of one database only. The server resource still exists, its configuration remains, and storage-related costs can still apply while compute is stopped. Azure Database for PostgreSQL intermediate 6 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 parameter A PostgreSQL parameter is a setting that tells the database how to behave. Some parameters affect performance, such as memory, autovacuum, query planning, or connection behavior. Others affect visibility, such as logging slow queries or enabling extension-related features. In Azure Database for PostgreSQL flexible server, you do not edit the server configuration file directly. Azure exposes supported parameters through portal, CLI, API, and templates. A parameter change can be harmless, helpful, restart-sensitive, noisy, or dangerous depending on what it controls and which workload depends on it. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL server parameter, PostgreSQL configuration parameter, postgresql.conf setting Quick peek Open full term page

Databases field-manual-complete PostgreSQL pgBouncer PostgreSQL PgBouncer is a connection pooler built into Azure Database for PostgreSQL flexible server. It helps when applications create many short-lived or idle database connections that would otherwise consume PostgreSQL server resources. Instead of every application connection becoming a heavy backend connection, PgBouncer reuses a smaller pool more efficiently. In Azure, it is enabled per server and reached through the same host using the PgBouncer port. It is especially useful for serverless apps, busy APIs, and applications with many clients, but it still needs testing with transactions and session behavior. PostgreSQL flexible server fundamentals 5 commands Aliases: PgBouncer, PostgreSQL connection pooler, built-in PgBouncer 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 private access PostgreSQL private access means the flexible server is reached through private networking instead of an internet-facing endpoint. The server sits in a delegated subnet in a virtual network, and clients resolve its name through Private DNS. Apps in the same virtual network, peered networks, VPN, or ExpressRoute can connect if routing and security rules allow it. For a learner, the key idea is simple: choose private access when the database should behave like an internal service, not a public database with firewall openings. PostgreSQL flexible server intermediate 5 commands Aliases: PostgreSQL private networking, PostgreSQL VNet integration, Private access for PostgreSQL flexible server, PostgreSQL delegated subnet access Quick peek Open full term page

Databases field-manual-complete PostgreSQL public access PostgreSQL public access means the flexible server has a public DNS name that can be reached over the internet, but only IP ranges you allow get a chance to connect. It is not anonymous access; users still need valid PostgreSQL credentials and encrypted connections. This option is useful when clients cannot use a virtual network, VPN, or ExpressRoute path. The important lesson is that public access is a controlled doorway, not a private network. The doorway needs tight firewall rules, ownership, and regular review. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL public endpoint, PostgreSQL allowed IP addresses, PostgreSQL firewall access, Public access for PostgreSQL flexible server Quick peek Open full term page

Databases field-manual-complete PostgreSQL Query Store PostgreSQL Query Store is a built-in performance history feature for Azure Database for PostgreSQL flexible server. Instead of guessing why the database became slow, teams can look at recorded query behavior over time: which queries ran often, which took longest, which waited on locks or I/O, and when the pattern changed. It is not a tuning magic button. It is evidence. Developers, DBAs, and operators use it to separate bad SQL, missing indexes, workload spikes, and application changes from general database health complaints. Data platform intermediate 5 commands Aliases: PostgreSQL Query Store, Azure PostgreSQL Query Store, pg_qs, Query Store for PostgreSQL flexible server Quick peek Open full term page

Databases field-manual-complete PostgreSQL read replica A PostgreSQL read replica is a second flexible server that follows a primary PostgreSQL server and accepts read-only traffic. Writes still go to the primary. The replica is useful when reporting, analytics, search indexing, or distant users are putting too much read pressure on the main database. Because replication is asynchronous, the replica can lag behind current writes. That lag matters. Learners should remember that a read replica is for read scale, regional reach, and recovery options, not for splitting ordinary writes across two active databases. PostgreSQL flexible server fundamentals 5 commands Aliases: PostgreSQL replica, PostgreSQL read-only replica, Azure PostgreSQL read replica, Read replica for PostgreSQL flexible server 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 A PostgreSQL server is the managed Azure resource that owns your PostgreSQL databases. It is not just one database; it is the parent container for databases, connection endpoints, administrator access, networking rules, backup settings, maintenance behavior, and server-level configuration. Developers connect to it through a PostgreSQL host name, while operators manage it through Azure. When someone says “the server is down,” they usually mean this resource is unavailable, misconfigured, overloaded,... Azure Database for PostgreSQL intermediate 5 commands Aliases: No aliases yet 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 server firewall A PostgreSQL server firewall is the public-network gate in front of an Azure Database for PostgreSQL flexible server. If public access is enabled, clients can attempt to connect only when their source IP address falls inside an allowed firewall rule. The rule does not grant database access, create a user, or bypass passwords. It simply lets the traffic reach the server endpoint. If the server uses private access instead, the... Data platform intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page

Databases field-manual-complete PostgreSQL server parameter A PostgreSQL server parameter is a setting that changes how the managed PostgreSQL server behaves. Some parameters affect performance, such as memory, autovacuum, query planning, or connection handling. Others affect visibility, such as logging, Query Store, extension behavior, or diagnostic output. In Azure Database for PostgreSQL flexible server, you do not edit postgresql.conf on the host. Azure exposes supported parameters through the portal, CLI, API, and templates. A parameter change... PostgreSQL intermediate 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 storage autogrow PostgreSQL storage autogrow is a safety valve for an Azure Database for PostgreSQL flexible server. When storage consumption gets too high, Azure can increase the server’s allocated storage instead of letting the database hit a disk-full condition. That protects writes, replication, and normal workload activity. It is not a cleanup tool and it does not shrink storage later. If tables, indexes, logs, or WAL files keep growing, autogrow buys time and continuity, but the bill and capacity footprint can keep rising until the workload is fixed. PostgreSQL flexible server advanced 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

Web premium App Service connection string A named connection string stored in App Service configuration and exposed to application code for supported database or service connectivity. It helps learners understand where the concept appears in Azure operations and what to verify before changing it. App Service intermediate 5 commands Aliases: app service connection string, connection string Quick peek Open full term page

Containers learning-path-anchor System node pool A system node pool is the AKS worker pool that keeps the cluster itself functioning. It hosts core Kubernetes and AKS add-on pods such as DNS, networking agents, metrics, and connectivity components. You can technically run application pods there, but experienced teams avoid that because noisy workloads can starve the services that make the... Azure Kubernetes Service intermediate 4 commands Aliases: AKS system pool, system mode node pool, AKS platform node pool, kube-system node pool Quick peek Open full term page

Databases learning-path-anchor Table A table is the basic place where structured data lives in a database. Each row is one record, and each column describes one attribute, such as customer ID, order date, amount, or status. In Azure, tables show up in Azure SQL Database, SQL Managed Instance, Synapse dedicated SQL pools, Fabric warehouses, PostgreSQL, MySQL, and... Database intermediate 4 commands Aliases: database table, SQL table, relational table, data table Quick peek Open full term page

Databases learning-path-anchor Temporary bytes Disk space used by temporary files created during queries, sorts, hashes, or joins. PostgreSQL advanced 4 commands Aliases: Temporary bytes, temporary bytes, Azure Temporary bytes, temp_bytes, Temporary Files Size, PostgreSQL temporary files Quick peek Open full term page

Databases premium Azure SQL logical server An Azure SQL logical server is a logical administrative construct for Azure SQL Database and related SQL resources. Microsoft Learn describes it as the central point for managing a collection of databases, including logins, firewall rules, auditing, threat detection policies, and failover groups. Azure SQL Database fundamentals 16 commands Aliases: No aliases yet Quick peek Open full term page

Analytics premium Synapse SQL Synapse SQL is the T-SQL analytics capability in Azure Synapse Analytics. It includes dedicated SQL pools for provisioned warehousing and serverless SQL pools for on-demand lake queries, letting teams analyze structured and semi-structured data through familiar SQL endpoints inside a Synapse workspace. Synapse Analytics intermediate 7 commands Aliases: Synapse SQL engine, Azure Synapse SQL, Synapse serverless and dedicated SQL, SQL analytics in Synapse Quick peek Open full term page

Databases premium Dead tuples Dead tuples are obsolete PostgreSQL row versions left behind by UPDATE or DELETE operations until VACUUM or autovacuum cleans them up; in Azure Database for PostgreSQL they are an important signal for bloat, storage growth, and query performance. PostgreSQL intermediate 6 commands Aliases: PostgreSQL dead tuples, dead row versions, table bloat tuples, MVCC dead rows Quick peek Open full term page

Networking premium ExpressRoute ExpressRoute lets organizations extend on-premises networks into Microsoft cloud services over private connectivity provided through a connectivity provider. Teams use it to connect datacenters, branches, or colocation environments to Azure with predictable private paths for workloads that need stronger latency, bandwidth, and routing control than public internet connections. It is not a VPN tunnel, a private endpoint, an internet performance guarantee, or proof that every connected application is secure, redundant, or correctly routed. In production, confirm circuit state, provider state, peering configuration, BGP routes, gateway SKU, connected virtual networks, bandwidth, metrics, DNS path, firewall path, and provider escalation details before. Hybrid connectivity intermediate 6 commands Aliases: Azure ExpressRoute, ExpressRoute circuit, private Microsoft cloud connectivity 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

Containers premium AKS private cluster Microsoft Learn describes a private AKS cluster as an Azure Kubernetes Service cluster whose API server uses internal IP addresses and Private Link-based connectivity. The design keeps control-plane traffic between the API server and node pools on private networking, with DNS configuration required for administrators and automation. AKS networking advanced 5 commands Aliases: Azure Kubernetes Service private cluster, aks private cluster Quick peek Open full term page

Web premium App Service VNet integration Microsoft Learn describes App Service virtual network integration as the feature that lets an App Service app access resources in or through an Azure virtual network. It affects outbound traffic from the app; inbound private access uses other controls, such as private endpoints and access restrictions. App Service Networking intermediate 5 commands Aliases: App Service virtual network integration, regional VNet integration, Web App VNet integration 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

Analytics premium Azure-SSIS integration runtime Azure-SSIS integration runtime is Azure Data Factory or Azure Synapse compute that lets organizations deploy, run, and manage SQL Server Integration Services packages in Azure. Data Factory intermediate 5 commands Aliases: Azure SSIS integration runtime, Azure-SSIS IR Quick peek Open full term page

Migration premium Backup vault A Backup vault is an Azure Backup storage and management entity that stores backups, recovery points, and backup policies for supported newer workloads. Backup and recovery fundamentals 5 commands Aliases: No aliases yet Quick peek Open full term page

Containers premium Connected registry an Azure Container Registry capability that keeps container images available in remote, edge, or intermittently connected environments by syncing with a parent registry Azure Container Registry intermediate 5 commands Aliases: No aliases yet Quick peek Open full term page