Azure Cosmos DB Key-Value Tables Core (SQL) vs Table API

Question

Both Core (SQL) API and Tables API work with data in Key-Value table. What are the considerations for choosing one over the other?

In practice is there a default choice ... like unless one needs to be able to:
a) condition 1
b) condition 2
c) condition 3

always choose Core (SQL) API / Table API?

From an exam point-of-view (DP-900 Azure Data Fundamentals) is there a correct/preferred answer if asked to choose an API for Key-Value table?

Answer 1

Hi, @JJ Sharma Welcome to the Microsoft Q&A forum, and thanks for reaching out.
Choosing between SQL API and Table API will primarily depend on the kind of data that you're going to store. SQL API provides a schema-less JSON database engine with SQL querying capabilities whereas Table API provides a key-value storage database service. Both SQL API and Table API are designed to store huge amounts of data. However, you may want to look into Azure Table Storage as well. Cosmos DB lets you fine-tune the throughput that you need and robust indexing/querying support and that comes at a price. Azure Tables on the other hand comes with fixed throughput and limited indexing/querying support and is extremely cheap compared to Cosmos DB.

always choose Core (SQL) API / Table API?
--SQL API is a document store for JSON data. The SQL API is the Core API for new applications.

From an exam point-of-view (DP-900 Azure Data Fundamentals) is there a correct/preferred answer if asked to choose an API for Key-Value table?
--Table API is ideal for existing Azure Storage Tables. It’s a key-value store.

Please refer to this document for more detailed information

Let me know if you are looking for any additional information

Regards
Geetha