I've seen "scalable" attribute in Sql DB and i want to know if it's the same for Mysql.

• Moved by Michael CurdMicrosoft employee Monday, August 03, 2015 9:28 PM Question more appropriate for this forum

Hi Davide,

One of the primary advantages of Platform-as-a-Service (PaaS) solutions offered by Microsoft Azure is the ease with which scaling can be implemented. Since this involves switching between pricing tiers and performance levels, we need to first identify the criteria used to distinguish between them.   

Effectively, Azure offers SQL Databases in the following three pricing tiers each associated with different performance characteristics and resiliency-related features

• Basic - designated as B in the Preview portal is geared towards small, single-user databases, typically ideal for
  development and testing. It is limited to 5 DTUs, its size cannot exceed 2 GB,
  and its Point In Time Restore window is limited to 7 days.
• Standard - constitutes the most common choice for production databases
  supporting workgroup and web applications. It scales up to 250 GB in size, with
  support for Standard Geo-Replication and Point In Time Restore window of 14
  days. It also offers three performance levels, labeled as S0, S1 , and S2 in the
  Preview portal, which give you, respectively, the performance levels of 10 DTUs, 20 DTUs, and 50 DTUs.
• Premium - is intended for enterprise grade applications with high
  concurrency levels. It scales up to 500 GB in size, with support for Active
  Geo-Replication and Point In Time Restore window of 35 days. Its performance
  levels range from P1, P2 , and P3 (as displayed in the Preview portal) yielding, respectively, the
  performance levels of 100 DTUs, 200 DTUs, and 800 DTUs.

The pricing tier and the performance level can be changed practically instananeously from either Azure
management portal or the Preview Portal (although users might experience temporarily dropped connections during the switch, so you should code your applications to handle such drops gracefully). The process can be automated by leveraging the Set-AzureSqlDatabase PowerShell cmdlet with the -ServiceObjective and -Edition parameters (representing the performance level and pricing tier). When scaling down, ensure that the database complies with the restrictions of the target pricing tier (in particular, in regard to the maximum size and replication scope).

see further details on Azure SQL Database here.

ClearDB Mysql scales by enabling you to select the type of database plan you would like to use but I think you should contact clearDB ( 3rd party service ) for further understanding on the same.

Regards,

Shirisha Paderu

• Edited by Casey KarstMicrosoft employee, Moderator 13 hours 45 minutes ago Edited Structure
• Proposed as answer by Casey KarstMicrosoft employee, Moderator 13 hours 45 minutes ago

Hi Davide,

One of the primary advantages of Platform-as-a-Service (PaaS) solutions offered by Microsoft Azure is the ease with which scaling can be implemented. Since this involves switching between pricing tiers and performance levels, we need to first identify the criteria used to distinguish between them.   

Effectively, Azure offers SQL Databases in the following three pricing tiers each associated with different performance characteristics and resiliency-related features

• Basic - designated as B in the Preview portal is geared towards small, single-user databases, typically ideal for
  development and testing. It is limited to 5 DTUs, its size cannot exceed 2 GB,
  and its Point In Time Restore window is limited to 7 days.
• Standard - constitutes the most common choice for production databases
  supporting workgroup and web applications. It scales up to 250 GB in size, with
  support for Standard Geo-Replication and Point In Time Restore window of 14
  days. It also offers three performance levels, labeled as S0, S1 , and S2 in the
  Preview portal, which give you, respectively, the performance levels of 10 DTUs, 20 DTUs, and 50 DTUs.
• Premium - is intended for enterprise grade applications with high
  concurrency levels. It scales up to 500 GB in size, with support for Active
  Geo-Replication and Point In Time Restore window of 35 days. Its performance
  levels range from P1, P2 , and P3 (as displayed in the Preview portal) yielding, respectively, the
  performance levels of 100 DTUs, 200 DTUs, and 800 DTUs.

The pricing tier and the performance level can be changed practically instananeously from either Azure
management portal or the Preview Portal (although users might experience temporarily dropped connections during the switch, so you should code your applications to handle such drops gracefully). The process can be automated by leveraging the Set-AzureSqlDatabase PowerShell cmdlet with the -ServiceObjective and -Edition parameters (representing the performance level and pricing tier). When scaling down, ensure that the database complies with the restrictions of the target pricing tier (in particular, in regard to the maximum size and replication scope).

see further details on Azure SQL Database here.

ClearDB Mysql scales by enabling you to select the type of database plan you would like to use but I think you should contact clearDB ( 3rd party service ) for further understanding on the same.

Regards,

Shirisha Paderu

• Edited by Casey KarstMicrosoft employee, Moderator Friday, August 07, 2015 5:23 PM Edited Structure
• Proposed as answer by Casey KarstMicrosoft employee, Moderator Friday, August 07, 2015 5:23 PM