zmorris
-
645 voteszmorris
gave this 3 votes
·
-
735 voteszmorris
gave this 3 votes
·
-
22 voteszmorris
gave this 1 vote
·
-
161 votes
Stay tuned, you will see the engagement model from Microsoft here change in the coming weeks. It’s great to see such an active and passionate community invested in making Windows Azure better, things will improve. Thanks for your patience and keep the ideas coming.
zmorris
gave this 3 votes
·
-
67 voteszmorris
gave this 3 votes
·
-
688 voteszmorris
gave this 1 vote
·
-
98 voteszmorris
gave this 3 votes
·
-
30 voteszmorris
gave this 3 votes
·
-
295 voteszmorris
gave this 1 vote
·
-
114 voteszmorris
gave this 1 vote
·
-
392 voteszmorris
gave this 3 votes
·
-
11 voteszmorris
gave this 1 vote
·
-
5 voteszmorris
shared this idea and gave it 3 votes
·
-
1 votezmorris
shared this idea and gave it 1 vote
·
-
410 voteszmorris
gave this 3 votes
·
-
605 votes
We do still intend to support secondary indexes. However, no firm timeline has been established for when that capability will be made available. Based on our most current information, secondary indexes are not going to be released as a feature in 2011.
zmorris
commented
·
MakerOfThings77 has a good idea. His suggestion would be a significant step in the right direction (ANY steps in ANY direction for Table Storage would be welcome at this point. Did Ballmer gut the storage team too....?)
zmorris
commented
·
seconded
zmorris
gave this 3 votes
·
-
910 votes
There are at least three ways to enable e-mail for your Azure applications:
1.Using a custom on-premise Email Forwarder Service.
2. Using Email Server’s Web Services APIs
3.Using a third party SMTP Service
All are described in more depth here: http://blogs.msdn.com/b/windowsazure/archive/2010/10/08/adoption-program-insights-sending-emails-from-windows-azure-part-1-of-2.aspx?wa=wsignin1.0
Please help us understand what scenarios (if any) these patterns don’t address for your applications.
zmorris
commented
·
seconded
zmorris
gave this 1 vote
·
This or some similar 'mass delete' capability is a must.
Having to retrieve entities first or having to know the entity partition and row key first and then issuing a separate delete request for every entity is not practical (and is expensive) for large historical tables (which is one of the primary use cases for table storage!).