Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You might be running into the SE_REPL* issues that are currently plaguing a lot of folks using Sql Azure (my company included).</p> <p>When you experience the timeouts, try checking your wait requests for wait types of:</p> <ul> <li>SE_REPL_SLOW_SECONDARY_THROTTLE</li> <li>SE_REPL_COMMIT_ACK</li> </ul> <p>Run the following to check your wait types on current connections:</p> <pre><code>SELECT TOP 10 r.session_id, r.plan_handle, r.sql_handle, r.request_id, r.start_time, r.status, r.command, r.database_id, r.user_id, r.wait_type, r.wait_time, r.last_wait_type, r.wait_resource, r.total_elapsed_time, r.cpu_time, r.transaction_isolation_level, r.row_count FROM sys.dm_exec_requests r </code></pre> <p>You can also check a history of sorts for this by running:</p> <pre><code>SELECT * FROM sys.dm_db_wait_stats ORDER BY wait_time_ms desc </code></pre> <p>If you're seeing a lot of SE_REPL* wait types and these are staying set on your connections for any length of time, then basically you're screwed. Microsoft are aware of the problem, but I've had a support ticket open for a week with them now and they're still working on it apparently.</p> <p>The SE_REPL* waits happen when the Sql Azure replication slaves fall behind. Basically the whole db suspends queries while replication catches up :/</p> <p>So essentially the aspect that makes Sql Azure highly available is causing databases to become randomly unavailable. I'd laugh at the irony if it wasn't killing us.</p> <p>Have a look at this thread for details: <a href="http://social.technet.microsoft.com/Forums/en-US/ssdsgetstarted/thread/c3003a28-8beb-4860-85b2-03cf6d0312a8">http://social.technet.microsoft.com/Forums/en-US/ssdsgetstarted/thread/c3003a28-8beb-4860-85b2-03cf6d0312a8</a></p>
    singulars
    1. This table or related slice is empty.
    1. POSQL Azure - One session locking entire DB for Update and Insert
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul DB
    1. USPaul DB
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSQL Azure - One session locking entire DB for Update and Insert
      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. VTUpMod
    1. COThanks a million Paul, you just confirmed the conclusion I can to! I'll update my post with the data I got out of it in case it helps others diagnose. I have also opened a support issue with MS about this. We're a gold partner, for all that counts, so hopefully we'll get an answer sometime before Christmas!
      singulars
      1. PO
      1. USSam Shiles
    2. CONo worries, sorry to hear you're having the same issues as we are. It's a serious problem and pretty much impossible to mitigate from a coding perspective.
      singulars
      1. PO
      1. USPaul DB
    3. COThanks a ton for this Paul, I've been encountering the same issues and have been hunting everywhere for a reasonable answer. This was my suspicion and your queries helped confirm it.
      singulars
      1. PO
      1. USDenis Pitcher
 

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