Monitoring errors after upgrade to SQL Monitor 10.2.1

RitaNzenwa

Just upgraded to 10.2.1.31696 and a number of SQL 2012 SP1 servers result in the exception: 'user_objects_deferred_dealloc_page_count'. This I see is fixed in SQLMonitorWeb_10.2.3.31956.exe - which I'm applying right now.

However, 2 Azure SQL 2017 databases also result in the exception: Operation failed. Operation will cause database event session memory to exceed allowed limit. Event session memory may be released by stopping active sessions or altering session memory options. Check sys.dm_xe_database_sessions for active sessions that can be stopped or altered. If no sessions are active on this database, please check sessions running on other databases under the same logical server.

I'm not sure if this is a database-related issue or a monitoring issue.Is the latter, is this fixed in the latest version of SQL Monitor? If so, where can I download this from?

Alex B

I don't believe the latter issue has been addressed.  Can you confirm if you are monitoring a large number of broadly inactive databases within a low DTU elastic pool where you are seeing this issue?

If that is not the case can you elaborate a bit more on the specific entity/entities you are seeing this with

RitaNzenwa

Hi Alex, its an elastic pool with two databases: 31.73GB and 530.87GB
As far as I can tell, they are both active, with low database resource utilization at the moment (screenshots attached)

RitaNzenwa

So, I thought before I go and rummage around in the database, I'd look up sys.dm_xe_database_sessions with regards to Azure SQL Database, and I found this article by Grant Fritchey

https://www.scarydba.com/2019/03/04/system_health-extended-events-in-azure-sql-database/

And he states: "While the system_health documentation says it applies to Azure SQL Database, there is not a system_health session there."
Could this be related to the issue.