<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Patterns: Windows Azure &amp;amp;ndash; Upgrading your table storage schema without disrupting your service</title><link>https://www.dotnetzone.gr:443/cs/blogs/pkefal/archive/2009/11/30/patterns-windows-azure-amp-ndash-upgrading-your-table-storage-schema-without-disrupting-your-service.aspx</link><description>In general, there are two kind of updates you’ll mainly perform on Windows Azure. One of them is changing your application’s logic (or so called business logic) e.g. the way you handle/read queues, or how you process data or even protocol updates etc</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator></channel></rss>