Reputation: 977
We want to store a large key-value pair set in Sql Azure (approx. 50GB) consisting of an MD5 hash key and an int value. The table will be not be written to after it has been populated and often queried. Queries will be for multiple keys ranging from between 6 and 5000 items at a time. Are there any best practices that we should follow, for example: is it okay to query using IN, should be chunk larger queries into smaller sections? Anything else we should be aware of.
Upvotes: 4
Views: 1517
Reputation: 5124
How complex will be your queries? Maybe you can consider alternatives to SQL server.
Azure storage tables - noSQL key-value storage great for storage of large amount of data, pretty fast for queries by partition key and row key, and cheap comparing to SQL. If you can make good partitioning and retrieve data (6-5000 items) as whole partitions, you are done. See comparision to SQL : https://msdn.microsoft.com/en-us/library/azure/jj553018.aspx
DocumentDB - another non-structured noSQL storage, more indexed and query-friendly than Azure Tables. http://azure.microsoft.com/en-us/services/documentdb/
Upvotes: 2