Mark Freeman
My feedback
25 results found
-
5 votesMark Freeman
supported this idea
·
-
2 votesMark Freeman
supported this idea
·
-
3 votes
We're currently reviewing this suggestion as part of general usability improvements.
Mark Freeman
supported this idea
·
-
4 votesMark Freeman
supported this idea
·
-
3 votesMark Freeman
supported this idea
·
-
4 votesMark Freeman
supported this idea
·
-
4 votesMark Freeman
supported this idea
·
-
9 votesMark Freeman
supported this idea
·
-
5 votesMark Freeman
supported this idea
·
-
2 votesMark Freeman
supported this idea
·
-
5 votesMark Freeman
supported this idea
·
-
4 votes
An error occurred while saving the comment Mark Freeman
supported this idea
·
-
2 votesMark Freeman
supported this idea
·
-
1 voteMark Freeman
shared this idea
·
-
1 voteMark Freeman
shared this idea
·
-
15 votes
An error occurred while saving the comment Mark Freeman
commented
I have 40 Azure SQL Databases in an Elastic Pool. I have a relatively resource-intensive custom metric I want to run daily. I want it to run outside of the work hours for the database users, and not at the same time in every database, which can cause problems at the pool level. Being able to set a timeout, a start time and either a delay between the execution in each database in the pool or a separate start time for each database would keep me from getting error alerts almost every day.
Mark Freeman
supported this idea
·
-
1 voteMark Freeman
shared this idea
·
-
7 votes
An error occurred while saving the comment Mark Freeman
commented
I would like to see Start and End columns or a Duration column, along with a Blocked Process Count.
When displaying the Process tab on the detail page, it would be helpful for each blocked process to display as a collapsed line in a tree, each branch of which can be expanded. Each line should display the SessionId, Start and End or Duration, and the Application, Host, User, and the first (n) characters of the SQL fragment. It is great to have all the details available, but I currently get one huge page with no navigation for one blocker (see attached) and it is very difficult to visualize the blocking tree to determine cause, effect, and duration, or even just to see everything that is impacted.
Documentation on how SQL Sentry handles this in their web interface:
https://documentation.solarwinds.com/en/success_center/sqlsentry/content/sqlsentry-portal/blocking.htm#:~:text=the%20%E2%96%BA%20arrow%20to-,expand%20the%20row,-and%20view%20theMark Freeman
supported this idea
·
-
11 votesMark Freeman
supported this idea
·
-
6 votesMark Freeman
supported this idea
·
Similarly, I had a set of servers for which no data was being collected due to authentication failures (something changed in our Azure Entra configuration for a subscription). The first I knew about it was when there was a performance problem I needed to investigate and found no data had been collected for weeks.