Greg Smulko (Redgate)
My feedback
19 results found
-
6 votes
An error occurred while saving the comment -
4 votesGreg Smulko (Redgate)
supported this idea
·
-
4 votesGreg Smulko (Redgate)
supported this idea
·
-
11 votesGreg Smulko (Redgate)
supported this idea
·
-
2 votesGreg Smulko (Redgate)
supported this idea
·
-
4 votesGreg Smulko (Redgate)
supported this idea
·
-
4 votesGreg Smulko (Redgate)
supported this idea
·
-
29 votesGreg Smulko (Redgate)
supported this idea
·
-
5 votesGreg Smulko (Redgate)
supported this idea
·
-
2 votes
An error occurred while saving the comment Greg Smulko (Redgate)
commented
Hey Chris, could you please expand on what exactly you would like to see?
I see that we have already the following in the UI:
- for deadlock there is `Host name`,
- for Long-running query there is `Host` in the Details tab and
- for Blocking process there is `Host` in the Processes tab.Do I understand correctly that you'd like to see "hostpid" in addition to Host name for the above, or is there anything else?
Greg Smulko (Redgate)
supported this idea
·
-
9 votesGreg Smulko (Redgate)
supported this idea
·
-
153 votes
Adam
responded
We’ve made some improvements in this area but will leave it open so you can continue to give us your suggestions
An error occurred while saving the comment Greg Smulko (Redgate)
commented
Hi @Phil, thanks for your comment. It is just to let you know that we are actively working on an alternative to MSSQL. Stay tuned. :)
-
3 votes
An error occurred while saving the comment Greg Smulko (Redgate)
commented
Hi Tibor,
We just released version 13.0.30 with an improvement where now it's possible to set to always redact query plan parameters, even for administrators, by setting the `SQLMONITOR_AlwaysRedactQueryPlanParameters` environment variable on the Website to `true`.
Note that before the query plan params were masked for Standard and Read-Only roles, but always available for Administrators.
One more thing worth mentioning: we redact values of the parameters that a query was run with, but if a sensitive value is hardcoded within a query (as opposed to being parametrized), there is not much we can to do reliably redact it - so we even don't attempt to do so.
Does it solve the issue for your use case?
-
176 votes
currently under investigation
Greg Smulko (Redgate)
supported this idea
·
-
8 votesGreg Smulko (Redgate)
supported this idea
·
-
16 votes
An error occurred while saving the comment Greg Smulko (Redgate)
commented
Great idea! Duplicate of https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/36257860-add-user-editable-notes-in-estate I believe?
Greg Smulko (Redgate)
supported this idea
·
-
60 votesGreg Smulko (Redgate)
supported this idea
·
An error occurred while saving the comment Greg Smulko (Redgate)
commented
I think this is fixed already?
-
33 votesGreg Smulko (Redgate)
supported this idea
·
-
73 votes
Daniel Rothig
responded
Thanks Phil – we are considering reworking the upgrade process. If this suggestions gains more traction, we’ll prioritise it higher
An error occurred while saving the comment Greg Smulko (Redgate)
commented
The unattended installation of SQL Monitor is possible as described in this article: https://documentation.red-gate.com/sm/installation-and-setup/automated-installation-and-updates .
It's still not as good as it could be, but definitely a step in the right direction IMO. :)
Hi @tgrove, that's a very fair point.
We've added support for moving groups as a byproduct of adding support for setting aliases from PowerShell, so at the moment only monitored entities that can be aliased support setting groups.
It seems like a relatively easy change though, so we'll try to get it over the line within the next couple of weeks.