If so, I apologize. In the editorial, I'm just giving an initial reaction to the CTP based on what a developer in a corporate context might be aiming for with a SQL Azure development, and expecting to be able to do.

I'm not entirely sure that the overwhelming demand is for simpler storage models in the cloud. It would certainly make life a lot simpler for implementation if there was. I'm quite interested in Quadrant's approach in that it aims to go beyond the simple table model to allow the editing of hierarchies and structured data. I'd also make the simple intuitive bulk loading of table data via the Houston interface a requirement given the scale of the data that is likely to be required for a production system. However,in the editorial, I was merely trying to argue that a top-down diagrammatic approach to creating Azure databases might actually be an easier route to a success than one that is based from the start at the table-level. An approach that allows the creating, editing, etc.. of tables is necessary of course, but surely not sufficient.