Azure table with different entities in development storage?

Still searching for an answer to this question:

It's my understanding that there is no requirement that there be any structural or type similarity between different entities in a table in Azure storage. But开发者_开发技巧 what about development storage? I recently read that this is not true as development storage requires a schema because it stores the data using SQL Server Express.

Can someone confirm this. Also if this is the case then how could I use Dev storage to model different entities within a table in production?

Thanks in advance

Gordon, Development Storage uses SQL server under the hood to simulate the live azure storage. (It must store the data somewhere). Think of it as an emulator. You use the same API to access live storage or development storage. You are not required to use a schema for development storage. Think of it as changing a connection string from a staging server to a production server.

Check out this link for more detailed information:

You are not required to use a schema in production, but all objects in a development storage table must have the same set of columns (see here). I'd suggest using multiple tables in development, and switching to one table in production if you need to (maybe use a configuration value to indicate what table tables to use?)