Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If I was to take a guess, I would assume that the background database load from the webserver is elevating locks and causing the whole thing to slow down. Then you take a large-ish query and run it and that causes lock (and resource) contension. </p> <p>I see this <em>ALL THE TIME</em> with companies complaining of performance problems with their client-server applications when going from one SQL server to a cluster. In the web-world, we get those issues much earlier.</p> <p>The solution (most times) to lock issues with one of the following: * Refactor your queries to work better (storing SCOPE_IDENTITY instead of calling it 5 times for example) * Use the <a href="http://www.sql-server-performance.com/articles/per/lock_contention_nolock_rowlock_p1.aspx" rel="nofollow noreferrer">NO LOCK statement</a> everywhere it makes sense.</p> <p>EDIT:</p> <p>Also, try viewing the server with the new 2008 SQL Management Studio <a href="http://www.sql-server-performance.com/articles/dba/%20New_Features_in%20_SSMSPart1_p1.aspx" rel="nofollow noreferrer">'Activity Monitor'</a>. You can find it by right-clicking on your server and selecting 'Activity Monitor'. </p> <ul> <li>Go to the Processes section and look at how many processes are 'waiting'. Your wait time should be near-0. If you see alot of stuff under 'Wait Type', post a screen shot and I can give you an idea of what the next step is.</li> <li>Go to the Resource Waits section and see what the numbers look like there. Your waiters should always be near-0.</li> <li>And 'Recent Expensive Queries' is awesome to look at to find out what you can do to improve your general performance.</li> </ul> <p>Edit #2:</p> <p>How much slower is it? Your SAN seems to be taking up about 10 seconds worth, but if you are talking 20 seconds vs. 360 seconds, then that would not be relevent, and there is no waits for locks, so I guess I am drawing a blank. If the differene is between 1 second and 10 seconds then it seems to be network related.</p>
    singulars
    1. This table or related slice is empty.
    1. POAsp.net sql server 2005 timeout issue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJasonRShaver
    1. USJasonRShaver
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs there a way to determine if the webserver would be causing this issue. Any tool or stats we can use. Our queries do have nolock wherever necessary
      singulars
      1. PO
      1. USuser55474
    2. COThese are the results from running dm_os_wait_stats for networkIo and write log ASYNC_NETWORK_IO 69613 160718 2046 2250 WRITELOG 4111 116125 1750 203
      singulars
      1. PO
      1. USuser55474
    3. COWhat does your SQL Server topology look like (edit your post with the answer). Are you using a SAN? Are you using a cluster? 70k waits is a bit odd, but the max was only 2 seconds so it is not likely your issue. Also, clear your wait stats (DBCC SQLPERF ('sys.dm_os_wait_stats', CLEAR)) and then run your query though the web server and repost the new wait_stats.
      singulars
      1. PO
      1. USJasonRShaver
 

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