In my previous article I showed how to asynchronously audit data in one instance with one central database that holds audited data from all other databases on that instance. So to continue showing the greatness that is Service Broker this article explains how to do the same with multiple servers or instances. This means that a single server holds audited data from all other servers. It's a classic many to one (one to many) scenario. Note that this technique works also if you want to send data from the master server to multiple children servers.
i haven't seen your until now... if i had... hell i wouldn't even bother just kidding! i would! Service Broker is a lot of fun! especially when it takes all of your servers resources with message poisoning
BACKUP CERTIFICATE CertificateAuditDataReceiver TO FILE = 'C:\CertificateAuditDataReceiver.cer'
GO
I get: Msg 15240, Level 16, State 1, Line 1 Cannot write into file 'C:\CertificateAuditDataReceiver.cer'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
I hav got a strange problem with this asynchronous auditing. My auditing is working fine if i send the messages one at a time. But when i make the system live it is not working. My live system has about 50 commands fired per minute (or more).The activation proc calls a c# program as well as a few xp_cmdshell commands. I hav set the max_queue_readers to 200. Can anybody help me out?? Thanks in advance...
Article: Centralized Asynchronous Auditing across Instances and Servers with Service Broker
Posted - 08/20/2007 : 08:03:31
