Hong Wang

My feedback

  1. 9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →
    Hong Wang commented  · 

    We have no plan to let user the innodb_flush_log_at_trx_commit. Setting the value to 0 or 2 will potential have unrecoverable data loss.

  2. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →
    Hong Wang commented  · 

    Thanks Jose for comments.
    Javier, please let us know if you need any specified permission. We can investigate your request.

  3. 6 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →

    wait_timeout and table_open_cache are now available to be changed in the service.

    To learn how to change the parameter values, view the docs:
    - Using the Azure portal: https://docs.microsoft.com/en-us/azure/mysql/howto-server-parameters
    - Using the Azure CLI: https://docs.microsoft.com/en-us/azure/mysql/howto-configure-server-parameters-using-cli

    Thanks,
    Andrea Lam on behalf of the Azure Database for MySQL product team

    Hong Wang commented  · 

    The wait_timeout is already opened for change. You can change it from Portal or CLI anytime.
    For other parameters, they are all memory related parameters and restricted by SKU chosen.

  4. 39 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →

    Support for up to five read-only replicas within the same region is now in public preview. This feature is aimed to scale out read-heavy workloads.

    Check out the documentation to learn more about replicas:
    - Overview: docs.microsoft.com/en-us/azure/mysql/concep..
    - How to create replicas from the portal: docs.microsoft.com/en-us/azure/mysql/howto-..

    Azure CLI support will be following shortly.

    Thanks,
    Andrea Lam on behalf of the Azure Database for MySQL product team

    Hong Wang commented  · 

    We are working on this now and will have it in the next few months. Follow us @AzureDBMySQL on Twitter for announcements of new features.

  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →
    Hong Wang commented  · 

    Today, the default value is 2000. Do you want to change it to bigger or smaller?

  6. 14 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  5 comments  ·  Azure Database for MySQL  ·  Flag idea as inappropriate…  ·  Admin →
    Hong Wang commented  · 

    The innodb_buffer_pool_size is the major memory setting for MySQL, it is fixed in different SKU. We will not let user to change it. You can only increase the SKU to get higher memory.

    For query_cache related setting, We are planning to expose to user with limited range.

Feedback and Knowledge Base