Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there an reference about how to properly design Table Storage data? What to put in the partition and what in the table? Are there any principals to follow(like ER model in SQL)?
In general, you need to ensure that your content-searching will be efficient. Data is stored based on partition key and indexed on row key. If, say, you have app ID as partition key and customer ID as row key, you’d have very fast searching for a customer. However: Imagine having to search by customer’s last name (another property). Now you’d need to do a table scan within the app’s partition. You might need a second table to map customer’s last name (as row key) to customer ID (a property).
To see some real-world guidance, take a look at this msdn article.