Databases
StackOverflow2013
Postsdbo
PODatabase locked (or slow) with Linq To Entities and Stored Procedures
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODatabase locked (or slow) with Linq To Entities and Stored Procedures
    primarykey
    data
    text
    <p>I'm using Linq To Entities (L2E) ONLY to map all my Stored Procedures in my database for easy translation into objects. My data is not really sensitive (so I'm considering Isolation level "READ UNCOMMITED" everywhere). I have several tables with millions of rows. I have the website and a bunch of scripts utilizing the same datamodel created using entity framework. I have indexed all tables (max 3 for each table) so that every filter I use is directly catched by an index. My scripts mainly consists of </p> <p>1) Get your from DB (~5 seconds) 2) Making API (1-3 seconds) 3) Adding result in database</p> <p>I have READ_COMMITTED_SNAPSHOT and ALLOW_SNAPSHOT_ISOLATION set to ON.</p> <p>Using this strategy most my queries is fixed and very fast (usually). I still have some queries used by my scripts that could run up to 20 second but the are not called that often.</p> <p>The problem is that suddenly the whole database gets slow and all my queries are returned slowly (can be over 10 seconds). Using Sql Profiler I have tried to find the issue.</p> <p>As mentioned Im considering NOLOCKS using "READ UNCOMMITED"... Right now I'm going through each possible database call and adding indexes and/or caching tables to make the call faster.</p> <p>I have also considered removing L2E and accesing the "old way" to be sure thats not the issue. Is My data context looking my tables? it sure looks that way. I have experimenting haveing the context living over the API call to minimize created context but right now I create a new context for each call since I thought it was looking the database.</p> <p>The problem is that I cannot control, that every single call is made fast, for all eternity otherwise the whole system gets slowed down.</p> <p>When I restart sql server and rebuild indexes its really fast for a short period of time before everything gets slow again. Any pointers would be appreciated. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USFischer
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODatabase locked (or slow) with Linq To Entities and Stored Procedures
      1. USJeffO
      1. VTFavorite
    2. VO
      singulars
      1. PODatabase locked (or slow) with Linq To Entities and Stored Procedures
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODatabase locked (or slow) with Linq To Entities and Stored Procedures
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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