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.
I’m wondering what the professional way is to create a database schema for a Azure Storage Tables database (not SQL Azure).
For a datawarehouse you usually make a starscheme or snowflake (OLAP cube) and for a database with a lot of transactions you’d probably make a normalized relational database (SQL Azure/SQL Server). But with Azure Storage Tables there aren’t any relations to make so what’s the best practice for creating a professional Azure Storage Tables database?
So, Azure Storage tables do not have schema. When you save an object to an azure table, that object is just there. You do not create schema for a table. Visualization tools, like Cerebrata’s Storage Studio or Visual Studio’s table viewer attempt to visualize the data in the azure table as columns, but in reality, all they’re doing is showing you properties of objects as columns for convenience.