locked
Using SQL Azure instead of Azure Storage Blob and Tables? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Is it a good Idea to use SQL Azure instead of Tables and Blobs from Azure Storage? How will it impact the Performance and scalability of the application? What are the best practices for Azure Backend?

    Regards, Vishal Supekar BE.CSE MCPDEA(Micorsoft Certified)
    Thursday, January 12, 2012 4:56 AM

Answers

  • Question
    Sign in to vote
    4
    Sign in to vote

    Gauruv's response is spot on. I'd only add a couple things to it:

    1. In their "vanilla" forms, Table Storage can scale larger than SQL Azure. SQL Azure instances are limited to 150GB, and there is currently no way to scale up (ie, more CPU/memory/etc). If you use SQL Azure Federations, then they can both potentially scale to very large sizes.
    2. Table Storage seems to be more reliable. I've been using both SQL Azure and table storage heavily for over a year. In that time I've had multiple outages and performance problems with SQL Azure. I've had no problems at all with Table Storage. 
    3. SQL Azure is still a SQL Server. You need to design it, optimize it, and manage it just like an on-premise SQL Server instance. Microsoft support generally will not help you figure out your locking issues, where you need indexes, how to write queries, etc. Because SQL Azure has a lower hardware spec than some on-premise installation, good design and good queries are even more important. 

    BKR

    Thursday, January 12, 2012 5:07 PM
  • Question
    Sign in to vote
    2
    Sign in to vote

    It actually depends on your application requirements. Azure Tables and Blobs provide very cheap storage where as SQL Azure is comparatively expensive. Furthermore Azure Tables does not have built-in transaction support as well as relational features available in SQL Azure.

    What I would recommend is that you analyze your application requirements from data management (CRUD) point of view and then decide which component (SQL Azure, Azure Tables, and Azure Blob Storage) is best for each requirement. You could come up with an architecture where you are using all three of them.

    Hope this helps.

    Thanks

    Gaurav Mantri

    Cerebrata Software

    http://www.cerebrata.com

     

    • Proposed as answer by Horizon_Net Thursday, January 12, 2012 10:28 AM
    • Marked as answer by Challen Fu Wednesday, January 18, 2012 7:33 AM
    Thursday, January 12, 2012 6:11 AM

All replies

  • Question
    Sign in to vote
    2
    Sign in to vote

    It actually depends on your application requirements. Azure Tables and Blobs provide very cheap storage where as SQL Azure is comparatively expensive. Furthermore Azure Tables does not have built-in transaction support as well as relational features available in SQL Azure.

    What I would recommend is that you analyze your application requirements from data management (CRUD) point of view and then decide which component (SQL Azure, Azure Tables, and Azure Blob Storage) is best for each requirement. You could come up with an architecture where you are using all three of them.

    Hope this helps.

    Thanks

    Gaurav Mantri

    Cerebrata Software

    http://www.cerebrata.com

     

    • Proposed as answer by Horizon_Net Thursday, January 12, 2012 10:28 AM
    • Marked as answer by Challen Fu Wednesday, January 18, 2012 7:33 AM
    Thursday, January 12, 2012 6:11 AM
  • Question
    Sign in to vote
    4
    Sign in to vote

    Gauruv's response is spot on. I'd only add a couple things to it:

    1. In their "vanilla" forms, Table Storage can scale larger than SQL Azure. SQL Azure instances are limited to 150GB, and there is currently no way to scale up (ie, more CPU/memory/etc). If you use SQL Azure Federations, then they can both potentially scale to very large sizes.
    2. Table Storage seems to be more reliable. I've been using both SQL Azure and table storage heavily for over a year. In that time I've had multiple outages and performance problems with SQL Azure. I've had no problems at all with Table Storage. 
    3. SQL Azure is still a SQL Server. You need to design it, optimize it, and manage it just like an on-premise SQL Server instance. Microsoft support generally will not help you figure out your locking issues, where you need indexes, how to write queries, etc. Because SQL Azure has a lower hardware spec than some on-premise installation, good design and good queries are even more important. 

    BKR

    Thursday, January 12, 2012 5:07 PM