TheSurfingDBA ✭✭✭

If you look in my script, I am first registering the computer and then registering the connection. Sounds like you have registered the SQL Virtual Instance name for the FCI but are missing the node. if you will use the Register-Computer cmdlet for the passive nodes you should be good to go. 

@"clementn" What version of SQL Sentry are you on?

This is great to hear!!!

Hi, do you have a support case number. I can track this down and see if we can get some movement on this?

He is the script I wrote minus any credential info <# # Load SwisPowerShell Import-Module SwisPowerShell # connect to SWIS - use your connection details and credentials $username = "" $password = "" $swis = Connect-Swis -Hostname <IP of Orion Server > -Credential ( Get-Credential -UserName $username -Message "Enter your…

I got it figured out. I had some weird errors but was able to get it running

Also another good perspective can be found in these articles regarding Wait-based performance tuning. * https://sqlperformance.com/2020/01/sql-performance/why-waits-alone-are-not-enough * https://www.sentryone.com/white-papers/troubleshooting-sql-server-wait-stats *…

CXPacket waits are not necessarily a bad thing. Eliminating all CXPackets waits means that your queries are running single threaded. We want large queries to go parallel. Did you get the performance expected when you saw high CXPackets? It is possible if a large query can't go parallel you are getting some funky execution…

 SELECT system_memory_state_desc FROM sys.dm_os_sys_memory This will tell you the [system_memory_state_desc] and if you are experiencing memory pressure at the OS layer. [system_memory_state_desc] has only 3 possible values.* Available physical memory is high * Available physical memory is low * Physical memory usage is…

yeah, just wanted to be sure there was no OS memory pressure, which can lead to server instability. next step will be tackling queries with high memory grants. Have you tried Erik Darlings sp_pressuredector. It can help as well diagnose some of this stuff. erikdarlingdata.com/sp_pressuredetector/

I look at this and see that the number of memory grants requested is possibly causing this alert to fire. PLE took a hit but recovered. These are relating to SQL Server Memory pressure If you are able to run this query ... SELECT SERVERPROPERTY('SERVERNAME') AS 'Instance', (SELECT value_in_use FROM sys.configurations WHERE…