LINQ statements for storing Windows Azure tables

Question

Table support currently supports From, Where, Take, and First.

Are there any plans to support any of the 29 operators?

Are there architectural or design methods for storage that must be followed to implement features such as COUNT, SUM, GROUP BY, etc.

If we need to code these ourselves, how much is the difference in performance, do we look at something like this through SQL and SQL Server? You see that this is somewhat comparable or will be much slower if I need to make a graph or a sum or group on a giant dataset?

I like the Azure platform and the idea of ​​cloud storage. I like Table Storage for the amount of data that it can store, and its schemas without limits. SQL Azure simply will not work due to the high cost of storage space.

Answer 1

The only alternative is to pull everything out locally and run Count () or Sum () on local objects. Since you must migrate the entire contents of your table before doing the count, this will certainly be much slower than doing something server-like, like with SQL. How much slower is the size of your data.

Answer 2

Ryan

As Steve said, aggregations are allowed by the client side, which can lead to poor performance if your datasets are too large.

An alternative is to think of the problem differently. You might want to pre-calculate these values ​​so that they are easily accessible. For example, if you have master part data (for example, a proverbial purchase order + line item), you might want to keep the “line item amount” in the header. This may seem "redundant" (and it is), but de-normalization is what you will need to consider.

These precomputations can be performed by "synch" or "asynch". In some situations, you can allow yourself to have approximations, so deferring calculations can be beneficial in terms of performance.