This is great Corey - thanks for sharing it! I would be very interested to see the perf numbers on this one. One question - being a service broker noob, I don't quite understand the relationship between the queue Uri and the queue created in the database. When I ran the tests I wound up with a user instance testqueue database, but poking around in there I couldn't see where / how the Uri used in the test (like "tcp://localhost:2204/h") was used - I mean, it works, just trying to understand how, is all. One of the benefits of Rhino Queues was since it's going over TCP it can be load balanced effectively - does the same apply here or would I be leaning on clustering database servers behind a single logical endpoint?
Thanks, Matt On Sun, Nov 1, 2009 at 7:11 AM, Corey Kaylor <[email protected]> wrote: > Yes in this case having sql installed is no different from msmq. However, > creating the schema for the queues and history tables etc. I have created a > somewhat flexible option if the account running the queues has enough > permission to create the database etc. it will create the schema for you as > a "user instance" mostly made for the unit tests. However, I would still > recommend for production systems that you create the schema manually with > the included sql scripts. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
