Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <pre><code>alter authorization on database::[&lt;your_SSB_DB&gt;] to [sa]; </code></pre> <p>The EXECUTE AS infrastructure requires <code>dbo</code> to map to a valid login. Service Broker uses the EXECUTE AS infrastructure to deliver the messages. A typical scenario that runs into this problem is a corporate laptop when working from home. You log in to the laptop using cached credentials, and you log in into the SQL using the same Windows cached credentials. You issue a <code>CREATE DATABASE</code> and the <code>dbo</code> gets mapped to your corporate domain account. However, the EXECUTE AS infrastructre <em>cannot</em> use the Windows cached accounts, it requires direct connectivity to the Active Directory. The maddening part is that things work fine the next day at office (your laptop is again in the corp network and can access to AD...). You go home in the evening, continue with Lesson 3... and all of the sudden it doesn't work anymore. Make the whole thing seem flimsy and unreliable. Is just the fact that AD conectivity is needed...</p> <p>Another scenatio that leads to the same problem is caused by the fact that databases reteint the SID of their creator (the Windows login that issues the <code>CREATE DATABASE</code>) when restored or attached. If you used a local account <code>PC1\Fred</code> when you create the DB and then copy/attach the database to PC2, the account is invalid on PC2 (it is scoped to PC1, of course). Again, not much is affected but EXECUTE AS is, and this causes Service Broker to give the error you see.</p> <p>And last example is when the DB is created by an user that later leaves the company and the AD account gets deleted. Seems like revenge from his part, but he's innocent. The production DB just stops working, simply because it's <em>his</em> SID that the <code>dbo</code> maps too. Fun... </p> <p>By simply changing the <code>dbo</code> to <code>sa</code> login you fix this whole EXECUTE AS thing and all the moving parts that depend on it (and SSB is probably the biggest dependency) start working.</p>
    singulars
    1. This table or related slice is empty.
    1. POSQL Server 2008 Service Broker tutorial -- cannot receive the message (exception in transmission_status)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlex
    1. USRemus Rusanu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSQL Server 2008 Service Broker tutorial -- cannot receive the message (exception in transmission_status)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COThat's it! Thanks a lot. I do not understand the details yet, but it simply works. Arthur C. Clarke: "Any sufficiently advanced technology is indistinguishable from magic." ... if one does not understand how it works. This way, you are a magician for me :)
      singulars
      1. PO
      1. USpepr
    2. CO+1 but I wish I could give you +100
      singulars
      1. PO
      1. USsmirkingman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload