Skip to content

Commit 60deab7

Browse files
authored
Merge pull request #96037 from matjazl/master
Remove references to Cosmos DB RU
2 parents 4238421 + 5b23e4a commit 60deab7

File tree

5 files changed

+34
-23
lines changed

5 files changed

+34
-23
lines changed

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43715,6 +43715,11 @@
4371543715
"source_path": "articles/aks/virtual-kubelet.md",
4371643716
"redirect_url": "/azure/aks/concepts-scale#burst-to-azure-container-instances",
4371743717
"redirect_document_id": false
43718+
},
43719+
{
43720+
"source_path": "articles/healthcare-apis/configure-cosmos-db.md",
43721+
"redirect_url": "/azure/healthcare-apis/configure-database",
43722+
"redirect_document_id": false
4371843723
}
4371943724
]
4372043725
}

articles/healthcare-apis/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@
2323
href: fhir-oss-cli-quickstart.md
2424
- name: Configure CORS
2525
href: configure-cross-origin-resource-sharing.md
26-
- name: Configure Cosmos DB
27-
href: configure-cosmos-db.md
26+
- name: Configure database settings
27+
href: configure-database.md
2828
- name: Use Custom HTTP headers to add data to Audit Logs
2929
href: use-custom-headers.md
3030
- name: Tutorials

articles/healthcare-apis/configure-cosmos-db.md

Lines changed: 0 additions & 21 deletions
This file was deleted.
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
---
2+
title: Configure database settings in Azure API for FHIR
3+
description: This article describes how to configure Database settings in Azure API for FHIR
4+
author: matjazl
5+
ms.service: healthcare-apis
6+
ms.subservice: fhir
7+
ms.topic: reference
8+
ms.date: 11/15/2019
9+
ms.author: matjazl
10+
---
11+
# Configure Database settings
12+
13+
Azure API for FHIR uses database to store its data. Performance of the underlying database depends on the number of Request Units (RU) selected during service provisioning or in database settings after the service has been provisioned.
14+
15+
Azure API for FHIR borrows the concept of RUs from Cosmos DB (see [Request Units in Azure Cosmos DB](https://docs.microsoft.com/azure/cosmos-db/request-units)) when setting the performance of underlying database.
16+
17+
Throughput must be provisioned to ensure that sufficient system resources are available for your database at all times. How many RUs you need for your application depends on operations you perform. Operations can range from simple read and writes to more complex queries.
18+
19+
> [!NOTE]
20+
> As different operations consume different number of RU, we return the actual number of RUs consumed in every API call in response header. This way you can profile the number of RUs consumed by your application.
21+
22+
To change this setting in the Azure portal, you can navigate to your Azure API for FHIR and open the Database blade, then change the Provisioned throughput to the desired value depending on your performance needs. You can change the value up to a maximum of 10,000 RU/s.* If you need a higher value, contact Azure support.
23+
24+
> [!NOTE]
25+
> Higher value means higher Azure API for FHIR throughput and higher cost of the service.
26+
27+
![Config Cosmos DB](media/database/database-settings.png)
41.1 KB
Loading

0 commit comments

Comments
 (0)