Piquet

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 
  2. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 
  3. 1,133 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    55 comments  ·  SQL Database  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  4. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  5. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  6. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  SQL Server » Other  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Piquet commented  · 

    For Read-Only databases there does not need to be a tick box on Maintenance Plan tasks that are designed to modify the database - these types of Tasks (e.g. Rebuild Index, Reorganize Index, Update Statistics, ...) should not even attempt to run on a database that is configured as Read-Only - Read-Only databases should be IGNORED (currently they are not and cause the Maintenance Plan to FAIL before completing the optimization Task on other "legitimate" databases).

    Piquet supported this idea  · 
  7. 67 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  7 comments  ·  SQL Server » Setup + Deployment  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  8. 3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  9. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →

    Hello Piquet
    Can you share more details here?
    (1) which version of SSMS you are using?
    (2) does this happen consistently or occasionally?
    (3) is it consistent with different versions of SQL or specific to a version?
    (4) does it show the status properly on the other replicas?

    thanks,
    Dinakar

    An error occurred while saving the comment
    Piquet commented  · 

    Also note: This is across multiple workstations and multiple users (i.e. my DBA colleagues) - I believe it is an omission in the product rather than a "bug" per se.

    An error occurred while saving the comment
    Piquet commented  · 

    G'day Dinakar,
    1) SSMS version 17.x (I would need to check when I am back on-site which specific v17.x version, but it is a relatively recent version
    2) Always (i.e. consistent) - the Object Explorer Databases folder NEVER shows any information about the role of an AlwaysOn Availability Group database - just it's Synch state.
    3) I could not say as we are only working with AlwaysOn with SQL server 2017 servers.
    4) The same issue applies to ALL replicas - that is part of the problem. i.e. in an Active-Active AlwaysOn pair (with 2x Availability Groups) there is no way of determining (from the MAIN Databases folder) if the connected to server is hosting the Primary of the Secondary)

    PK

    Piquet shared this idea  · 
  10. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet supported this idea  · 
  11. 22 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  SQL Server » Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 
  12. 19 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  17 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Piquet commented  · 

    Thanks for the info re CU4.
    Unfortunately "...only the latest cumulative update is available for download from Microsoft".
    CU5 is the earliest cumulative update that we downloaded (we installed SQL 2017 RTM and then applied CU5).
    Thus we are stuck with rolling back to RTM to avoid this bug!

    Piquet shared this idea  · 
  13. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 
  14. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 
  15. 1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  1 comment  ·  SQL Server » Bugs  ·  Flag idea as inappropriate…  ·  Admin →
    Piquet shared this idea  · 

Feedback and Knowledge Base