I've been working on a project to do high-volume audit logging for a large ESB with SQL Service Broker. We're using SQL Express on the logging client to host the initiator queue and SQL Enterprise to host the target queue. For some reason, processing messages out of the target queue peaks at a couple of hundred messages per second, even on a quad processor machine with plenty of RAM, and then SQL Server starts consuming about 95% of the CPU. This article on SSB performance shed some light on the need for multiple conversations, which helped a little but didn't solve the problem. Time to file a trouble ticket with MS. :(
Comments