documentation says that when you establish a event notification 'a number of conversations' will be started to the service...is there some why to estimate how many conversations are going to be started?
I have an instance (2012) that is starting almost 20 conversations to my srvc for tracking login/out/failure events.
Does this seem tooooo high for conversation count?
Whereas I have another event notification database scoped (tracking ddl stuff) that only starts one thread to my service.
is it cause my first event notif is server scoped... that it is creating soooo many conversations?
any insights would be lovely.
cheers.
-mt
mike t.