Merge pull request #79709 from ThomasWeiss/thweiss-cosmosdb-support-improvements

Various adjustments following support case reviews

Author: v-shils

articles/cosmos-db/find-request-unit-charge.md

@@ -4,7 +4,7 @@ description: Learn how to find the request unit (RU) charge for any operation ex
 author: ThomasWeiss
 ms.service: cosmos-db
 ms.topic: sample
-ms.date: 05/23/2019
+ms.date: 06/14/2019
 ms.author: thweiss
 ---
 # Find the request unit charge in Azure Cosmos DB
@@ -296,3 +296,4 @@ To learn about optimizing your RU consumption, see these articles:
 * [Globally scale provisioned throughput](scaling-throughput.md)
 * [Provision throughput on containers and databases](set-throughput.md)
 * [Provision throughput for a container](how-to-provision-container-throughput.md)
+* [Monitor and debug with metrics in Azure Cosmos DB](use-metrics.md)

articles/cosmos-db/index-policy.md

@@ -4,7 +4,7 @@ description:  Learn how to configure and change the default indexing policy for
 author: ThomasWeiss
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 05/20/2019
+ms.date: 06/14/2019
 ms.author: thweiss
 ---
 
@@ -14,6 +14,9 @@ In Azure Cosmos DB, every container has an indexing policy that dictates how the
 
 In some situations, you may want to override this automatic behavior to better suit your requirements. You can customize a container's indexing policy by setting its *indexing mode*, and include or exclude *property paths*.
 
+> [!NOTE]
+> The method of updating indexing policies described in this article only applies to Azure Cosmos DB's SQL (Core) API.
+
 ## Indexing mode
 
 Azure Cosmos DB supports two indexing modes:

articles/cosmos-db/media/set-throughput/coll-level-throughput.png

@@ -4,7 +4,7 @@ description: Learn about how to specify and estimate Request Unit requirements i
 author: rimman
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 05/20/2019
+ms.date: 06/14/2019
 ms.author: rimman
 
 ---
@@ -70,3 +70,4 @@ While you estimate the number of RUs per second to provision, consider the follo
 * Learn how to [optimize provisioned throughput cost in Azure Cosmos DB](optimize-cost-throughput.md).
 * Learn how to [optimize reads and writes cost in Azure Cosmos DB](optimize-cost-reads-writes.md).
 * Learn how to [optimize query cost in Azure Cosmos DB](optimize-cost-queries.md).
+* Learn how to [use metrics to monitor throughput](use-metrics.md).

articles/cosmos-db/request-units.md

@@ -4,7 +4,7 @@ description: Learn how to set provisioned throughput for your Azure Cosmos conta
 author: rimman
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 05/28/2019
+ms.date: 06/14/2019
 ms.author: rimman
 
 ---
@@ -68,6 +68,9 @@ You can combine the two models. Provisioning throughput on both the database and
 
 * You can create an Azure Cosmos database named *Z* with provisioned throughput of *"K"* RUs. 
 * Next, create five containers named *A*, *B*, *C*, *D*, and *E* within the database. When creating container B, make sure to enable **Provision dedicated throughput for this container** option and explicitly configure *"P"* RUs of provisioned throughput on this container. Note that you can configure shared and dedicated throughput only when creating the database and container. 
+
+   ![Setting the throughput at the container-level](./media/set-throughput/coll-level-throughput.png)
+
 * The *"K"* RUs throughput is shared across the four containers *A*, *C*, *D*, and *E*. The exact amount of throughput available to *A*, *C*, *D*, or *E* varies. There are no SLAs for each individual container’s throughput.
 * The container named *B* is guaranteed to get the *"P"* RUs throughput all the time. It's backed by SLAs.
 

articles/cosmos-db/set-throughput.md

@@ -4,7 +4,7 @@ description: This article introduces the concepts such as stored procedures, tri
 author: markjbrown
 ms.service: cosmos-db
 ms.topic: conceptual
-ms.date: 05/21/2019
+ms.date: 06/14/2019
 ms.author: mjbrown
 ms.reviewer: sngun
 
@@ -71,7 +71,7 @@ JavaScript functions are also subject to [provisioned throughput capacity](reque
 
 ## Triggers
 
-This section describes the two types of triggers:
+Azure Cosmos DB supports two types of triggers:
 
 ### Pre-triggers
 
@@ -81,6 +81,9 @@ Azure Cosmos DB provides triggers that can be invoked by performing an operation
 
 Similar to pre-triggers, post-triggers, are also associated with an operation on an Azure Cosmos DB item and they don’t require any input parameters. They run *after* the operation has completed and have access to the response message that is sent to the client. For examples, see [How to write triggers](how-to-write-stored-procedures-triggers-udfs.md#triggers) article.
 
+> [!NOTE]
+> Registered triggers don't run automatically when their corresponding operations (create / delete / replace / update) happen. They have to be explicitly called when executing these operations. To learn more, see [how to run triggers](how-to-use-stored-procedures-triggers-udfs.md#pre-triggers) article.
+
 ## <a id="udfs"></a>User-defined functions
 
 User-defined functions (UDFs) are used to extend the SQL API query language syntax and implement custom business logic easily. They can be called only within queries. UDFs do not have access to the context object and are meant to be used as compute only JavaScript. Therefore, UDFs can be run on secondary replicas. For examples, see [How to write user-defined functions](how-to-write-stored-procedures-triggers-udfs.md#udfs) article.