Monitoring errors after upgrade to SQL Monitor 10.2.1
RitaNzenwa
Posts: 4 New member
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?
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?
Tagged:
Answers
If that is not the case can you elaborate a bit more on the specific entity/entities you are seeing this with
Have you visited our Help Center?
As far as I can tell, they are both active, with low database resource utilization at the moment (screenshots attached)
Could this be related to the issue.