Windows Azure WADLogs Query is very slow -

I've found that to query a wadis table eg WADLogs are very slow, it takes 10 minutes back to 5 minutes.

Yes, the WAD table in our scenario is very big, however, I was not expecting this slow pace.

Question I:

1. Can someone please share the best way to manage the WED table so that the query is fast.

2. Is there any way to optimize the Wad tablet

3. Is a good practice of what should be done? And when should

4. Are there any best practices on purifying / support etc?

   Thank you.

   The Proud Minister explains how to ask wade tables in an executable manner. The lower line is that you should ask about partitioning and blocking to avoid execution-killing table scans. Tickcount has been included in the partitions for the wade table in a little encoded form and the properly constructed value can be used for range queries.