I'd start by telling you that when you think about Azure Table storage, forget everything you ever knew about RDBMS. :) Its intended for things that a relational storage system simply can't deal with.
For example, you want to access students by name, you'd have one table that's structured that way. If you want to get students in a class, you may have a single table for that class with a list of all the students in it. There are no join queres and highly redudant data isn't a bad thing.
Its a significnt shift in thinking as it does tend to go against everything we know about storing data. But when you're looking at building highly scalable systems without the infrastructure overhead that you get from trying to set up large scale on-premise systems (SANs, SQL Clusters, etc...).
- 已标记为答案 shimo 2012年4月12日 18:57
Thanks a lot
In this case I should use SQL Azure for storing data but I need to know what are benefits of blobs?
can i use SQL Azure also instead of storage table and blobs OR I should use SQL Azure for storing structured data and Blobs for storing unstructured
Thanks in advance
Blobs, unless you're using a TON of storage, will generally be cheaper then SQL Azure for pure storage. However, you will need to be aware of the transaction charges associated with deliverin the blobs (you pay per transaction for Azure Storage, but not for SQL Azure).
Most folks will recommend a mix of the two, SQL Azure for structure relationl storage, Azure Storage Blobs for binary storage.
BTW, when dealing with SQL Azure, be sure to also make sure you have retry and backoff strategies in place. SQL Azure is a shared resource model so just because you can take up 300 worker processes today doesn't mean you will be able to do it tomorrow. You'll want to make sure your application can handle faults and timed out connections as it comes under higher loads.
- 已标记为答案 shimo 2012年4月13日 7:06
2012年4月13日 7:08Thanks a lot for your help