Core Sql vs Azure Table

Question

Core Sql vs Azure Table

Peter Bons 156

So we have this scenario we think Cosmos DB table API is a good fit, or at least we want to investigate this. Now, according to this MS Learn module we should never choose for the table api, instead use the core api:

This API should only be used to allow existing apps that are based on the Table API access to Azure Cosmos DB. However, new projects should always choose Core (SQL).

Is this the official take and is it indeed discouraged to use the table api for new development as I can't find this in any of the docs.

Anurag Sharma 17,636 Reputation points

2021-10-13T05:36:53.793+00:00

Hi @Peter Bons , welcome to Microsoft Q&A forum.

The choice of API totally depends on requirements. SQL API is recommended as it offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries. Any new feature that is rolled out to Azure Cosmos DB is first available on SQL API accounts.

However, I am reaching out to product group internally to check on this and will get back at soon as I receive the response.
Peter Bons 156 Reputation points

2021-10-13T06:18:53.027+00:00

Great thanks!

SQL API is recommended as it offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries.

I understand, yet in my case we are dealing with a very large number of rows which I think the Table Api is a very good fit. But if it is nearing end-of-life obviously I do not want to go that way.

I'll await the response from the product group.
Anurag Sharma 17,636 Reputation points

2021-10-13T06:57:22.913+00:00

Thanks for your response. I am pretty much confident that Azure Cosmos Table API will be there as new SDKs are also coming.

Announcing the new Azure Tables Libraries

Just waiting for the internal team to confirm it as well.

Accepted answer

0 additional answers

Your answer

Anurag Sharma 17,636 Reputation points

2021-10-13T05:36:53.793+00:00

Hi @Peter Bons , welcome to Microsoft Q&A forum.

The choice of API totally depends on requirements. SQL API is recommended as it offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries. Any new feature that is rolled out to Azure Cosmos DB is first available on SQL API accounts.

However, I am reaching out to product group internally to check on this and will get back at soon as I receive the response.
Peter Bons 156 Reputation points

2021-10-13T06:18:53.027+00:00

Great thanks!

SQL API is recommended as it offers the best end-to-end experience as we have full control over the interface, service, and the SDK client libraries.

I understand, yet in my case we are dealing with a very large number of rows which I think the Table Api is a very good fit. But if it is nearing end-of-life obviously I do not want to go that way.

I'll await the response from the product group.
Anurag Sharma 17,636 Reputation points

2021-10-13T06:57:22.913+00:00

Thanks for your response. I am pretty much confident that Azure Cosmos Table API will be there as new SDKs are also coming.

Announcing the new Azure Tables Libraries

Just waiting for the internal team to confirm it as well.

Answer 1

Hi @Peter Bons , thanks for your patience. I have received the reply back from product group.

There is no plan to stop supporting Table API, and any service which gets retired Microsoft announces well in advance giving lot of time to everyone who is using it.

However, if you are using the Azure Cosmos DB and can model the data that suits SQL API, this would still be better as not only it offers better capabilities but cost/efficiency benefits as well.

----------

Please don't forgot to click on accept it as answer button wherever the information provided helps you. This can be beneficial to other community members as well.

Share via

Core Sql vs Azure Table

0 additional answers

Your answer