User profile for Alex Bartley

Hi kherrmann , The query shown is the SQL Database Sampler which runs every 15 seconds. Based on https://www.sqlskills.com/help/waits/preemptive_os_lookupaccountsid/ it looks like the wait is likely occurring due to the SUSER_SNAME(db.owner_sid) [owner] which is associated with the PREEMPTIVE_OS_LOOKUPACCOUNTSID wait. It seems this can be related to performance issues with the DC's or potentially round trip time to the servers. Kind regards, Alex / comments Official comment

Hi kherrmann ,The query shown is the SQL Database Sampler which runs every 15 seconds. Based on https://www.sqlskills.com/help/waits/preemptive_os_lookupaccountsid/ it looks like the wait is likely...

0 votes

Hi Al, Great to hear, glad that's sorted it for you! Kind regards, Alex / comments

Hi Al,Great to hear, glad that's sorted it for you! Kind regards,Alex

0 votes

Hi Al, You are most welcome! There are three that are normally in tempdb: one for Top Queries, one for query wait stats, and one for sproc stats (related to the Top procedures). If you look at the tables in tempdb > tables, you should see the a and b tables dbo.redgate_sqlmonitor_topqueries_<a|b>_xxxxxx, dbo.redgate_sqlmonitor_SprocStats_<a|b>_xxxxxx but you will no longer see the dbo.##redgate_sqlmonitor_querywaitstats_<a|b>_xxxxxx tables in the tempdb > Temporary Tables section. And in the product, if you go to the Top queries section, expand one of the entries and then scroll down to the table that has “Wait type” as the first column header, you should not see any data there for any of the queries. Kind regards, Alex / comments

Hi Al,You are most welcome!There are three that are normally in tempdb: one for Top Queries, one for query wait stats, and one for sproc stats (related to the Top procedures).If you look at the tab...

1 vote

Hi Al, It's worth noting that when SQL Server dumps like that, it's a SQL Server issue - the T-SQL being run is valid - and MS support should be passing the information from the stack dumps to the SQL Server team to investigate and fix. Having said that, I understand it's important to prevent your servers going down because of that by disabling the sampler, and so those steps are as follows: Find the ConfigurationFileEditor.exe tool included under the C:\Program Files\Red Gate\Redgate Monitor\BaseMonitor\Tools directory of a Base Monitor installation. Right click and run the tool as an Admin Click on the Load Configuration File option and then select the "RedGate.Monitor.BaseMonitor.exe.settings.config" which should be residing under the C:\ProgramData\Red Gate\Redgate Monitor directory by defaultIt's recommended that you save a copy of the config file elsewhere before editing it further though it should also save a copy itself. Once you've loaded the config file, find the [Cluster].[SqlServer].[TopQueries].[QueryWaitStats] channel, check the box next to it, then select the dropdown box and choose “Disabled” [image] Then click the disk save icon at the top left of the utility: [image] Once you have done that, please then restart the Base Monitor service The above will disable the sampler for all the entities you are monitoring. You can then edit the XML that is added to the RedGate.Monitor.BaseMonitor.exe.settings.config file as described on this documentation page https://documentation.red-gate.com/monitor/monitoring-servers-without-sysadmin-permissions-239667635.html in step 4b to add the clusterName and sqlServerName properties to the XMl to disable it specifically for the one entity. The clusterName is the top level name seen in Redgate Monitor and the sqlServerName is the portion that comes after the backslash "\" in the entity names. Both should be in all lower case to match what is seen in Redgate Monitor, except for (local) instances which are internally represented as an empty string “” . An example of this for my Windows VM named WinVM with a default SQL instance on it, I would have this as the XML between the <collectionSchedules> tags: <schedule qualifiedChannelName="[Cluster].[SqlServer].[TopQueries].[QueryWaitStats]" clusterName="winvm" sqlServerName=""> <disabledSchedule /> </schedule> I hope that helps, but please do let me know if you have any further questions and if you need specific help with this for your entity, please raise a support ticket referencing this forum post and we can reply there for your specific case. Kind regards, Alex / comments Official comment

Hi Al,It's worth noting that when SQL Server dumps like that, it's a SQL Server issue - the T-SQL being run is valid - and MS support should be passing the information from the stack dumps to the S...

0 votes

How can we help you today?

Alex Bartley

Comments