Opserver icon indicating copy to clipboard operation
Opserver copied to clipboard

No data of Performance, Memory&Storage, Cache and Waits on SQL Dashboard

Open nickluu2018 opened this issue 7 years ago • 3 comments

Given sp_Blitz(*) have installed on the SQL instance, there is no show data of Performance, Memory&Storage, Cache and Waits on SQL Dashboard. Testing on both version "master" and "overhaul" but no luck.

Do I miss any thing? Thanks.

nickluu2018 avatar Dec 07 '18 05:12 nickluu2018

I have a scenario like this:

  • 2 independent servers, ServerA and ServerB, with Opserver running on both servers and monitoring SQL Express 2008 R2 on servers itself and also each other, everything working fine. Both instances default named as MSSQLSERVER and connection strings as: "connectionString": "Data Source=ServerIP;Initial Catalog=master;Persist Security Info=True;User ID=UID;Password=PWD"
  • Recently on ServerA, uninstalled SQL Express 2008 R2 and installed SQL Express 2014 SP2. New instance named as MSSQLSERVER2014
  • Using same connection strings, the counters for Performance, Memory & Storage, Cache and Waits for ServerA stopped displaying on both servers but working fine for ServerB on both. (Debugging Opserver on development system in VS 2017 shows data available in Model.CurrentInstance but not rendering on client). However, other tabs like top, active, connections, databases are working fine.
  • Setting connection string for ServerA with instance as "connectionString": "Data Source=ServerA-IP\MSSQLSERVER2014;Initial Catalog=master;Persist Security Info=True;User ID=UID;Password=PWD" displays all counters on ServerA but not working on ServerB for ServerA. Tried some other patterns for connection string but none worked, most of them result in unable to connect

OpServer commit in use: Dec 07, 2018

haraman21 avatar Mar 30 '19 07:03 haraman21

Further digging into Model.CurrentInstance.PerfCounters.Data

  • ObjectName is being stored in the format "MSSQL$INSTANCENAME:xxxxx", as in my case MSSQL$MSSQLSERVER2014
  • For remote connection, setting ServerIP\InstanceName as Data Source in connectionString results in connection failure.
  • When only ServerIP is set as Data Source, system connects but SQLInstance sets ObjectName as "SQLServer", therefore, no data could be fetched for Performance ... Waits counters
  • Passing "ObjectName": "MSSQL$INSTANCENAME" along with connectionString in SQLSettings.json resolved the issue.

Hope this helps anyone looking for similar issue.

haraman21 avatar Mar 30 '19 20:03 haraman21

I know this is an old thread, but could you give an example of how this connection string is formatted?

TheAccidentalDBA avatar Jul 01 '21 14:07 TheAccidentalDBA