Databases
StackOverflow2013
Postsdbo
POSQL Server procedure timing out
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSQL Server procedure timing out
    primarykey
    data
    text
    <p>I'm having intermediate timeouts when calling this stored procedure from ASP.NET frontend environment on a production site. it returns the following sql exception:</p> <blockquote> <p>Exception Details: System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.</p> </blockquote> <p>Funny thing is, when executing this procedure on the server, or from a remote pc using Management Studio, it executes in 6s. But yet, sometimes times out from when executed from the ASP.NET application? Can this query be improved? Or is this issue related to something else? Anyone who can help? I;ve read some threads about increasing the timeout and enabling pooling on the connectionstring in my web.config, but haven't tried that yet.</p> <pre><code> ALTER PROCEDURE [dbo].[Report_Activity] ( @StartDate DATETIME , @EndDate DATETIME , @TotalActions INT OUTPUT ) AS BEGIN SELECT @TotalActions = COUNT(EventHistoryId) FROM dbo.SessionEventHistory WHERE DateCreated BETWEEN @StartDate AND @EndDate SELECT EventDescription, COUNT(EventHistoryId) AS EventCount FROM dbo.SessionEventHistory WHERE DateCreated BETWEEN @StartDate AND @EndDate GROUP BY EventDescription ORDER BY EventDescription </code></pre> <p>SQL SCHEMAS:</p> <pre><code>CREATE TABLE [dbo].[SessionEventHistory]( [EventHistoryID] [int] IDENTITY(1,1) NOT NULL, [SessionHistoryID] [int] NOT NULL, [CategoryID] [int] NULL, [UserName] [nvarchar](50) NULL, [IPAddress] [nvarchar](20) NOT NULL, [EventDescription] [nvarchar](1000) NOT NULL, [EventData] [varbinary](max) NULL, [DateCreated] [datetime] NOT NULL, CONSTRAINT [PK_UserEventHistory] PRIMARY KEY CLUSTERED ( [EventHistoryID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO ALTER TABLE [dbo].[SessionEventHistory] ADD CONSTRAINT [DF_UserEventHistory_DateCreated] DEFAULT (getdate()) FOR [DateCreated] GO </code></pre> <p>Table has 3 indexes:</p> <pre><code>/****** Object: Index [IX_SessionEventHistory_SessionHistoryId_CategoryId] Script Date: 07/04/2012 10:47:06 ******/ CREATE NONCLUSTERED INDEX [IX_SessionEventHistory_SessionHistoryId_CategoryId] ON [dbo].[SessionEventHistory] ( [SessionHistoryID] ASC, [CategoryID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO /****** Object: Index [IX_SessionEventHistory_UserName_DateCreated] Script Date: 07/04/2012 10:47:09 ******/ CREATE NONCLUSTERED INDEX [IX_SessionEventHistory_UserName_DateCreated] ON [dbo].[SessionEventHistory] ( [UserName] ASC, [DateCreated] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO /****** Object: Index [PK_UserEventHistory] Script Date: 07/04/2012 10:47:14 ******/ ALTER TABLE [dbo].[SessionEventHistory] ADD CONSTRAINT [PK_UserEventHistory] PRIMARY KEY CLUSTERED ( [EventHistoryID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO </code></pre> <p><strong>EDIT</strong></p> <p>I added the following Index, does it look okay?</p> <pre><code>CREATE NONCLUSTERED INDEX [IX_SessionEventHistory_DateCreated] ON [dbo].[SessionEventHistory] ( [DateCreated] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] GO </code></pre> <p><img src="https://i.stack.imgur.com/PKKeg.jpg" alt="enter image description here"></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAaron Bertrand
    1. USFaNIX
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSQL Server procedure timing out
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSQL Server procedure timing out
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSQL Server procedure timing out
      1. USRon
      1. VTFavorite
    1. COPutting an index on [DateCreated] would probably help
      singulars
      1. POSQL Server procedure timing out
      1. USDJ.
    2. CO@DJ I agree, that index will probably help overall efficiency, but if the same query with the same parameters behaves differently from different applications, there's probably more to it than that.
      singulars
      1. POSQL Server procedure timing out
      1. USAaron Bertrand
    3. COThere is already an index on DateCreated (IX_SessionEventHistory_UserName_DateCreated) ?
      singulars
      1. POSQL Server procedure timing out
      1. USFaNIX
 

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