1
1
---
2
2
title : Troubleshoot query issues when using Azure Cosmos DB
3
3
description : Learn how to identify, diagnose, and troubleshoot Azure Cosmos DB SQL query issues.
4
- author : ginamr
4
+ author : timsander1
5
5
ms.service : cosmos-db
6
6
ms.topic : troubleshooting
7
- ms.date : 01/14 /2020
8
- ms.author : girobins
7
+ ms.date : 02/10 /2020
8
+ ms.author : tisande
9
9
ms.subservice : cosmosdb-sql
10
10
ms.reviewer : sngun
11
11
---
@@ -192,7 +192,7 @@ While queries with a filter and an `ORDER BY` clause will normally utilize a ran
192
192
Query:
193
193
194
194
``` sql
195
- SELECT * FROM c WHERE c .foodGroup = “ Soups, Sauces, and Gravies” ORDER BY c ._ts ASC
195
+ SELECT * FROM c WHERE c .foodGroup = " Soups, Sauces, and Gravies" ORDER BY c ._ts ASC
196
196
```
197
197
198
198
Indexing policy:
@@ -302,7 +302,7 @@ For example, if we create a container with the partition key foodGroup, the foll
302
302
303
303
``` sql
304
304
SELECT * FROM c
305
- WHERE c .foodGroup = “ Soups, Sauces, and Gravies” and c .description = " Mushroom, oyster, raw"
305
+ WHERE c .foodGroup = " Soups, Sauces, and Gravies" and c .description = " Mushroom, oyster, raw"
306
306
```
307
307
308
308
These queries would also be optimized by including the partition key in the query:
@@ -321,7 +321,7 @@ WHERE c.description = "Mushroom, oyster, raw"
321
321
322
322
``` sql
323
323
SELECT * FROM c
324
- WHERE c .foodGroup > “ Soups, Sauces, and Gravies” and c .description = " Mushroom, oyster, raw"
324
+ WHERE c .foodGroup > " Soups, Sauces, and Gravies" and c .description = " Mushroom, oyster, raw"
325
325
```
326
326
327
327
## Filters on multiple properties
0 commit comments