Quantcast
Channel: SQL Service Broker forum
Viewing all articles
Browse latest Browse all 461

Large Number of entries in msdb.sys.conversation_endpoints for 'SQL/Notifications/ProcessWMIEventProviderNotification/v1.0' - tempDB lock?

$
0
0

Hello. This is my first time asking a question so apologies if I miss some details/protocol.

My question is twofold.

1: I have a large number of entries (200K+) within msdb.sys.conversation_endpoints for the service name 'SQL/Notifications/ProcessWMIEventProviderNotification/v1.0' (see below query) - does this sound correct. From what I understand, Service Broker converstations should be closed after use and cleaned up (deleted) after around 30 min. It would seem strange that there would be over 200K+ active conversations??

SELECT COUNT(conversation_handle)
--SELECT TOP 10 DATEADD(SECOND,-2147483647 ,lifetime) AS MessageDate, *
FROM msdb.sys.conversation_endpoints WITH(NOLOCK)
WHERE far_service = 'SQL/Notifications/ProcessWMIEventProviderNotification/v1.0'
AND state_desc = 'STARTED_OUTBOUND'

2: My second question relates to the first, hense the same thread. Does having such a large number of these open conversations lock pages in the tempDB and if so, is there some performance impact? I have uneven growth with 1 file in the tempdb (I have 8) and it's not possible to grow the other files to match 'tempdev' without increasing the drive space.

Some tech details:

@@Version = Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64)   Aug 19 2014 12:21:34   Copyright (c) Microsoft Corporation  Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 

Instance is clustered

- I have some WMI based alerts configured (failed logins, file growth, deadlocks)

I watched https://www.youtube.com/watch?v=5MGlqCfG1p0, where the speaker indicated Service Broker will hold locks to pages in the TempDB.

Thank you in advance for any help.

Allan


Viewing all articles
Browse latest Browse all 461

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>