Service Broker — many SQL servers in one domain. How to deploy?
===

I have the following situation. There is one central SQL Server (2008 R2, Standard Edition) and more (say 10) technological SQL Servers (2008 R2, Express). The technological servers are located near "real" machines, and they capture data from sensors. The data are to be passed to the central SQL Server to be processed somehow. All machines are located in the same domain.The Service Broker was chosen to send the data to the central Server. 

I have tried the standard MSDN tutorials [Completing a Conversation Between Instances][1] that shows how to create users without login, the certificates, etc. To summarize, it is quite a lot of things that are to be parametrized. No problem with manual settings for two servers, but...

 1. What is usual approach when working with more servers? If the servers are to be added in future, is it reasonable to insert the parameters (computer names, ports, etc.) into some configuration table or to create some stored procedures with hardwired constants... to be able to (re)construct the communication channels for newly added SQL servers?

 2. All the SQL servers are located within the same domain. Is it reasonable to simplify the deployment by not creating the users and the certificates? I have found the Remus Rusanu's answer on [Service broker with only domain account][2] on how to do that? Would you use the approach in real environment? What are the pros and cons?

Thanks, Petr


  [1]: http://msdn.microsoft.com/en-us/library/bb839483%28v=sql.105%29
  [2]: http://stackoverflow.com/a/11438275/1346705