Table Storage design question: Is it a good idea to use 1 table to store multiple types? RRS feed

  • Question

  • I'm just wondering if anyone who has experience on Azure Table Storage could comment on if it is a good idea to use 1 table to store multiple types?

    The reason I want to do this is so I can do transactions.  However, I also want to get a sense in terms of development, would this approach be easy or messy to handle?  So far, I'm using Azure Storage Explorer to assist development and viewing multiple types in one table has been messy. 

    To give an example, say I'm designing a community site of blogs, if I store all blog posts, categories, comments in one table, what problems would I encounter? On ther other hand, if I don't then how do I ensure some consistency on category and post for example (assume 1 post can have one 1 category)? 

    Or are there any other different approaches people take to get around this problem using table storage?

    Thank you,


    Wednesday, December 22, 2010 3:30 AM


  • Hi ray247,

    As far as I know, there isn't performane issue for storing multiple types in one table, however, it would be more complex to operate the table with clr code.


    Mog Liang
    • Marked as answer by Mog Liang Wednesday, December 29, 2010 9:22 AM
    Thursday, December 23, 2010 7:21 AM