Comments
Sort by recent activity
Hi @and1 If the queries are all parameterized, then the only user role that can see the query parameters are Admin role users. All other user roles are not able to see the parameters used. If the queries are hardcoded with sensitive data values, then these would be viewable to anyone who has access to SQL Monitor and the specific entity that the query was run on. In this case restricting the user to be able to view only entities they need to would help limit this, but they would still be visible to the users with access and there isn't a built in way to prevent this (other than disabling the sampling of the SQL Processes and Top queries. Kind regards, Alex / comments
Hi @and1 If the queries are all parameterized, then the only user role that can see the query parameters are Admin role users. All other user roles are not able to see the parameters used.If the q...
Hi @SteveLowe, Unfortunately there is not a way to do this; the alert will fire when the job fails the first time. I've found this Uservoice suggestion that seems to match what you are looking for, so please vote on it and add any comments you may have to clarify if needed https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/44520282-create-a-threshold-for-how-many-times-a-job-can-fa Kind regards, Alex / comments
Hi @SteveLowe,Unfortunately there is not a way to do this; the alert will fire when the job fails the first time.I've found this Uservoice suggestion that seems to match what you are looking for, s...
Hi ptotham, There isn't a built in way to track this and as for a custom metric, it would only be able to report on a single scalar value (likely the number of aborted sessions) but it wouldn't show you any other information that you are looking for, it would just be the number of aborted sessions. Please raisie a Uservoice suggestion here https://sqlmonitor.uservoice.com/forums/91743-suggestions/filters/top Kind regards, Alex / comments
Hi ptotham,There isn't a built in way to track this and as for a custom metric, it would only be able to report on a single scalar value (likely the number of aborted sessions) but it wouldn't show...
Hi @SEarle86, As discussed in the ticket raised this appears to be related to the functionality that Triggers use Row-level versioning and can take up space in the version store even if one of the associated isolation levels is not enabled (https://www.itprotoday.com/sql-server/triggers-and-version-store). You mentioned this article https://techcommunity.microsoft.com/t5/sql-server-blog/managing-tempdb-in-sql-server-tempdb-basics-version-store-why-do/ba-p/383509 that shows this happened in SQL 2005. Kind regards, Alex / comments
Hi @SEarle86,As discussed in the ticket raised this appears to be related to the functionality that Triggers use Row-level versioning and can take up space in the version store even if one of the a...
Hi Henry, Thank you for following up here and apologies that the functionality which was implemented didn't help in this case. I've fed this back to the team for consideration and you should also raise it on the SQL Monitor Uservoice here https://sqlmonitor.uservoice.com/forums/91743-suggestions/filters/top Kind regards, Alex / comments
Hi Henry,Thank you for following up here and apologies that the functionality which was implemented didn't help in this case. I've fed this back to the team for consideration and you should also ra...
Hi @hcuk94, The team are planning to implement Azure Active Directory Password and Azure Active Directory Integrated Authentication methods. Looking through some information on the Azure Service Principal and from what you've said, I think that may cover your need, but I'm not well versed with it, so do let me know if that is not the case - and if not, what the use case of that is over the two methods we are planning to implement. Kind regards, Alex / comments
Hi @hcuk94,The team are planning to implement Azure Active Directory Password and Azure Active Directory Integrated Authentication methods. Looking through some information on the Azure Service Pr...
Hi @hcuk94 , Currently there is not a way
to do this other than providing the server admin created when creating
the Azure SQL Server the database resides on using SQL Auth.
One
of the teams will be looking into authenticating to the entities using
Azure AD in the near future and so this may be considered in that and
I've mentioned this post to them.
You should also vote on
the Uservoice suggestion
https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/44685457-provide-aad-authentication-mode-to-connect-to-azur
and comment any specifics like the use of Azure Service Principals as
well. Kind regards, Alex
/ comments
Hi @hcuk94 ,Currently there is not a way
to do this other than providing the server admin created when creating
the Azure SQL Server the database resides on using SQL Auth.
One
of the teams wi...
Hi handrew, Looking at https://apphub.webex.com/applications/incoming-webhooks-cisco-systems-38054-23307-75252 and the error you are getting, Do you just need to use the custom webhook message and include a "text": or "markdwon": entry in the json? Kind regards, Alex / comments
Hi handrew,Looking at https://apphub.webex.com/applications/incoming-webhooks-cisco-systems-38054-23307-75252 and the error you are getting, Do you just need to use the custom webhook message and i...
Hi @Murad, I'm not sure then, that is an explanation that fits the data and the version shown. We'd probably need to look at the logs for that time period, but we only really support the last two major versions. So I'd suggest opening a support ticket if you have a valid support and upgrades contract. If not, you could download the log files from Configuration > Retrieve all log files and look in the Base Monitor_Sampling.<date>.log files for any connection issues for that entity at that time period. The log files are in UTC time. Kind regards, Alex / comments
Hi @Murad,I'm not sure then, that is an explanation that fits the data and the version shown. We'd probably need to look at the logs for that time period, but we only really support the last two m...
Hi @Murad It's likely that the primary node of the Windows Server failover cluster (WSFC) changed for those 4 hours (and the original primary went down) and then was failed back afterwards. In that version, the page will only show the machine level data for the currently active WSFC node that the SQL FCI is running on so the current primary node was down for those 4 hours (but the SQL FCI was still up as it had failed over to the other node). If you were to fail the monitored entity (the SQL 2012 cluster) over to the other node, you would see different machine level data. In later versions, it shows the data for the WSFC node that was active at that time (so the gap would instead have machine level data from the other node). Kind regards, Alex / comments
Hi @MuradIt's likely that the primary node of the Windows Server failover cluster (WSFC) changed for those 4 hours (and the original primary went down) and then was failed back afterwards. In that...