Blaž Dakskobler
My feedback
15 results found
-
10 votes
An error occurred while saving the comment -
13 votesBlaž Dakskobler supported this idea ·
-
21 votes
An error occurred while saving the comment Blaž Dakskobler commented@Redgate: Consider adding these votes to https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/33130783-total-data-file-size-used-metrics-add-filegroup
It's not identical, but close enough.
Blaž Dakskobler shared this idea · -
19 votesBlaž Dakskobler shared this idea ·
-
5 votes
An error occurred while saving the comment Blaž Dakskobler commentedThis is better now (not sure when the change was made... I noticed it on 7.1.4+)... the metric selector is changing width depending on the metric name length. Maybe a bit jerky, but still much better than before.
Blaž Dakskobler supported this idea · -
14 votesBlaž Dakskobler shared this idea ·
-
114 votes
Good idea! If this suggestion gets more traction, we’ll implement this.
An error occurred while saving the comment Blaž Dakskobler commentedTake into account heap fragmentation as well
-
30 votesBlaž Dakskobler supported this idea ·
-
27 votesBlaž Dakskobler shared this idea ·
-
41 votesBlaž Dakskobler supported this idea ·
-
98 votesDaniel Rothig responded
Thanks for the suggestion – we’ll monitor how popular it gets
Blaž Dakskobler supported this idea · -
126 votes
An error occurred while saving the comment Blaž Dakskobler commentedWell, an alternative idea to achieve this (i.e. to eliminate spike noise) is to enchance zooming / dragging in Analysis graph with an option to "lock" X-axis and only zoom/drag along Y-axis (the suggestion was merged here, so I'm reposting it).
An error occurred while saving the comment Blaž Dakskobler commentedIndeed - in case of extreme spikes you don't see the details you want to, making the graph useless unless you "zoom in" to a shorter time period, thereby often losing overview of the long term baseline.
Blaž Dakskobler supported this idea · -
45 votes
-
14 votes
We’re reviewing this and would appreciate any more context on what you would like to do with the information.
Blaž Dakskobler supported this idea · -
83 votesDaniel Rothig responded
We like the idea – if this idea gains traction, we’ll look into implementing something like this
Blaž Dakskobler supported this idea ·
First, consider changing the way you handle autogrowth, since it's better to keep DB files sized the same. See this for more info: https://www.mssqltips.com/sqlservertip/4937/expand-all-database-files-simultaneously-using-sql-server-2016-autogrowallfiles/
Saying that, check if these custom metrics I wrote can help you out:
https://sqlmonitormetrics.red-gate.com/percentage-of-usedavailable-database-space/
https://sqlmonitormetrics.red-gate.com/database-growth-steps-available/