Comments
Sort by recent activity
Hi @... 1. We don't have recommendations/minimum specs for Azure SQL DB as the repository. I will say to ensure the storage tier related to it has sufficient throughput to allow it to keep up with the amount of data being sampled/inserted and served to the web UI by the Base Monitor service, though what that is, depends on how many entities you are monitoring and how busy they are. 2. There is not a built-in export option and I would suggest to raise a Redgate Monitor Uservoice suggestion here https://sqlmonitor.uservoice.com/forums/91743-suggestions/filters/top. You can also remove and not tick the box to delete the entity data, which will keep the historical data until it is purged, or as stated above, suspend monitoring and ensure a license is not being consumed by the entity on the Configuration > Monitored servers page. Kind regards, Alex / comments
Hi @... 1. We don't have recommendations/minimum specs for Azure SQL DB as the repository. I will say to ensure the storage tier related to it has sufficient throughput to allow it to keep up wit...
Hi all, After working with @easby in a ticket, the issue is that an old view from v10 remained in the repository that had the same name as a new table being introduced. Running this before updating (or on the repository database after updating and getting the error above) should allow the schema upgrade to continue: DROP VIEW [settings].[MonitoredEntities]
Kind regards, Alex / comments
Hi all,After working with @easby in a ticket, the issue is that an old view from v10 remained in the repository that had the same name as a new table being introduced. Running this before updating...
Hi @ThomasBE, The view should already have been dropped in Seq284-Seq285 (around v10.0.8-v10.0.13) and this won't affect anyone that started on a version later than 10.0.13. The schema upgrade that included the T-SQL to drop the VIEW shows that it has run so either the view was recreated manually afterwards, or there was a modification of the entries in the data repository to cause it to skip the schema step that dropped it to think it was run when it was not. Kind regards, Alex / comments
Hi @ThomasBE,The view should already have been dropped in Seq284-Seq285 (around v10.0.8-v10.0.13) and this won't affect anyone that started on a version later than 10.0.13. The schema upgrade that...
Hi @easby, We'll need to get the log files and have a look at what is going on. I will reach out to you via a support ticket to get that and some further information and then will update here once we have a resolution. Kind regards, Alex / comments
Hi @easby,We'll need to get the log files and have a look at what is going on. I will reach out to you via a support ticket to get that and some further information and then will update here once ...
Hi @..., The narrowest time period you can set the focus window to is 15 minutes, so you can see what is occurring during the 15 minute focus window. The Top Queries section is gathered from various sys.dm_exec_* DMVs (see this page) and represents aggregate information for queries that have completed during the focus window time frame. There is also the SQL User Processes (top 10 by CPU), which gathers data from sys.sysprocesses (see this page) and is information on the process that is (or was) running at that time. This can show queries that have not ended yet. You can use the "Back in Time" mode (see this page) to go back to a specific date/time where you can then set the focus window to a 15 minute minimum time period. Kind regards, Alex / comments
Hi @...,The narrowest time period you can set the focus window to is 15 minutes, so you can see what is occurring during the 15 minute focus window.The Top Queries section is gathered from various ...
Hi @wkrouth Righto, I think I've figured it out. The problem is the quoting around the data connection string. It needs to be single quotes on the outside with double quotes around the connection string itself. 'DATACONNECTION="Data Source=**********,3342;Initial Catalog=**********;User ID=**********;Password=**********;Max Pool Size=500;Connect Timeout=15;Encrypt=True;Trust Server Certificate=False;Packet Size=8000"',In both the unquoted and single inside double quoted example it was causing the mandatory DATACONNECTION parameter to be missed and that's what caused msiexec to pop up the window. Please give that a try and let me know if it now works and I'll work on updating the documentation. Kind regards, Alex / comments
Hi @wkrouth Righto, I think I've figured it out. The problem is the quoting around the data connection string. It needs to be single quotes on the outside with double quotes around the connection...
Hi @wkrouth, It looks like you don't have the connection string enclosed in single quotes inside the double quotes. It should look like this with single quotes ' after the equal = sign and before the ending double quote ". "DATACONNECTION='<Connection string>'", that is "DATACONNECTION='Data Source=**********;Initial Catalog=**********;User ID=**********;Password=**********;Max Pool Size=500;Connect Timeout=15;Encrypt=True;Trust Server Certificate=False;Packet Size=8000'", Does that change the behavior? Kind regards, Alex / comments
Hi @wkrouth,It looks like you don't have the connection string enclosed in single quotes inside the double quotes. It should look like this with single quotes ' after the equal = sign and before t...
Hi @hayko1998, Does yours say "Start time:" or "Start time (estimated):"? If it says "Start time", it will be the start_time of the query as seen in sys.dm_exec_requests If it says "Start time (estimated):" then it will be the sqlserver_start_time of the SQL Server instance from sys.dm_os_sys_info. Kind regards, Alex / comments
Hi @hayko1998,Does yours say "Start time:" or "Start time (estimated):"? If it says "Start time", it will be the start_time of the query as seen in sys.dm_exec_requestsIf it says "Start time (esti...
Hi @hayko1998, The "Processes" tab shows the head blocker at the top and then the blocking chain of all blocked processes. [image] [image] The time shown for the blocked processes (highlighted in yellow) is the Start time of the process, not when it started being blocked. So it sounds like you have received a blocking alert and some of the processes that are blocked are ones that started several days ago, but are only now being blocked by the process the alert was raised for. If that doesn't help or doesn't seem to be the case, then please share a screenshot as above or text of the Processes tab and we can have a further look. If you aren't able to share that here, let me know and we can reach out via a support ticket. Kind regards, Alex / comments
Hi @hayko1998,The "Processes" tab shows the head blocker at the top and then the blocking chain of all blocked processes. The time shown for the blocked processes (highlighted in yellow) is the Sta...
Hi @Ed_Nasc, Two things to check - Did you previously see the root\MSCluster namespace and remove it? If so, you would need to remove the entity, ticking the box to delete the data, and then re-add it to SQL Monitor so it discovers it as a standalone machine rather than a cluster. Also, if you uncheck the option "Auto detect cluster name" when adding the entity, this will cause SQL Monitor to treat it as a cluster as this option should only be used when adding a Windows Server Failover Cluster (WSFC) in Azure as the CNO isn't accessible outside the cluster in Azure. Kind regards, Alex / comments
Hi @Ed_Nasc,Two things to check - Did you previously see the root\MSCluster namespace and remove it? If so, you would need to remove the entity, ticking the box to delete the data, and then re-add...