title: Prevent machine name being appended to endpoint name
body: <p>We have a fair number of services which we've already developed with NServiceBus, and we're just in the process of switching from using the MSMQ transport to using SQL Server transport.</p>
  
  <p>For the NSB Hosted services, this has been relatively straightforward. But we're having an issue with setting up some of our websites (asp.net web api).</p>
  
  <p>We're self-hosting within the websites, with the following configuration:</p>
  
  <pre><code>NServiceBus.Configure.Serialization.Xml();
  var bus = NServiceBus.Configure.With(/* specific assemblies */)
              .CastleWindsorBuilder(container)
              .DefineEndpointName(
                  ConfigurationManager.AppSettings["nsb:EndpointName"])
              .DefiningCommandsAs(t =&gt;
                  t.GetCustomAttributes(typeof(/* our marker */), false)
                       .GetLength(0) &gt; 0)
              .DefiningEventsAs(t =&gt;
                  t.GetCustomAttributes(typeof(/* our marker */), false)
                       .GetLength(0) &gt; 0)
              .SetEndpointSLA(new TimeSpan(0,10,0))
              .UseNHibernateTimeoutPersister()
              .UseNHibernateSubscriptionPersister()
              .UseTransport&lt;SqlServer&gt;() //&lt;-- Changed here
              .UnicastBus()
              .LoadMessageHandlers()
              //.DoNotCreateQueues()  //We create queues manually.
              .CreateBus()
              ;
  </code></pre>
  
  <p>The only lines I've changed are the <code>UseTransport&lt;&gt;</code> line (which previously had <code>Msmq</code>), and, temporarily, the <code>.DoNotCreateQueues()</code> line because I wanted to force it to create the queue tables (whilst I'm running locally under IIS express)</p>
  
  <p>The issue is, when it creates the queue tables, it's appending my machine name onto the name of the "base" table. I.e. the tables it creates (when the <code>EndpointName</code> app setting is <code>Service.Name</code>) are of the form:</p>
  
  <pre><code>Service.Name.MYMACHINENAME
  Service.Name.Retries
  Service.Name.Timeouts
  Service.Name.TimeoutsDispatcher
  </code></pre>
  
  <p>Whereas when it creates MSMQ queues, it creates:</p>
  
  <pre><code>Service.Name
  Service.Name.Retries
  Service.Name.Timeouts
  Service.Name.TimeoutsDispatcher
  </code></pre>
  
  <p>And, indeed, Subscribers that have already been updated to the SQL Server transport are looking for the <code>Service.Name</code> queue table to register their subscriptions.</p>
  
  <p>What am I doing wrong or what other information is required to work this out?</p>