2. Exceedra + Azure Mark Rendle Principal Software Architect
Dot Net Solutions Ltd.
@MarkRendle

3. Overview The Application Exceedra Procast Sales Planner
Analytics over historical sales data
Sales promotion planning
Comprehensive reporting solution
Fast, intuitive UX

4. Overview Application Architecture
The Procast application is built across multiple Microsoft technologies:
SQL Server 2008
Reporting Services
WCF web services
WPF Smart Client (XBAP)

5. Original Architecture
On-premise server
Web site & services, static files, database, reporting services…

6. Migration path SQL Server → SQL Azure
Mostly a direct copy, except for:
Use XQuery instead of OPEN XML
Explicit creation of Temp Tables
Performance tuning/tracing tooling
SQL Azure doesn’t support OPEN XML – better performance on XQuery anyway
No support for SELECT INTO

7. Migration path On-premise → Azure
The WCF service application was running in IIS on Windows Server Moving it into Azure was a simple matter of adding the project as a Web Role in a Cloud project in Visual Studio 2010.

8. Migration path On-premise → Azure The easy job. Just check:
Session handling
Application state
Now investigating Azure AppFabric Cache for performance boost

9. Migration path SQL Server Reporting Services → SQL Azure Reporting
Upload .rdl files to Azure Portal.
Tweak authorisation code in WPF client.

10. Migration path Static file hosting
Hosting the WPF XBAP files in Blob Storage reduces load on the Web Roles and cuts costs.

11. Azure Architecture Windows Azure Compute
Web application & WCF Services
Windows Azure Compute
Exceedra IP in Stored Procedures
SQL Azure
Complex analytics and planning reports
SQL Azure Reporting
Static file serving – XBAP, images…
Windows Azure Storage

12. © 2008 Microsoft Corporation. All rights reserved
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.