Skip to content

Fina

My feedback

3 results found

  1. 57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Fina commented  · 

    This is very much needed to monitor Azure SQL Databases, it's a big blind spot.

    Fina supported this idea  · 
  2. 15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    under review  ·  Neil Turner responded

    A great suggestion. We are exploring this as part of a wider review into improving query tuning features.

    Fina supported this idea  · 
    An error occurred while saving the comment
    Fina commented  · 

    The fact that there is no metadata saved alongside the tracked query is a huge limitation for the feature. It is very difficult to distinguish between queries—especially when many begin with similar SQL statements (e.g., SELECT followed by a list of columns). Adding support for an alias, ID, or even a comment field to indicate the purpose of tracking and the responsible user or team would significantly improve the feature’s utility.

  3. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Suggestions  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Fina shared this idea  · 

Feedback and Knowledge Base