StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15773268
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
5
CommunityOwnedDate
CreationDate
2013-04-02T20:00:09.737
FavoriteCount
0
LastActivityDate
2015-01-21T17:48:26.173
LastEditDate
2015-01-21T17:48:26.173
LastEditorUserId
196319
OwnerUserId
196319
ParentId
15772252
PostTypeId
2
Score
23
ViewCount
0
LastEditorDisplayName
text
Body
So I had a similar issue a couple of weeks ago, which was explained to me by one of our DBAs thusly (paraphrased and dumbed down to my level of course): When a SQL Server stored procedure is called, the server creates and caches an execution plan per stored procedure per <code>object_id</code>. Sometimes a bad execution plan can be created by SQL Server depending on the parameter value that is passed in (in our case it was null for a nullable parameter). When this happens, the quick fix is to run <code>sp_recompile 'Schema.Procedure'</code> in SQL Server Management Studio (or whatever DB management tool you might be using). All this does is clear the plan cache for that stored procedure. If the next callee of the proc passes in the "bad" parameter value again you'll be stuck in the same situation so the real fix is to give the query a hint using the <code>OPTIMIZE FOR</code> syntax (see <a href="http://msdn.microsoft.com/en-gb/library/ms181714.aspx">http://msdn.microsoft.com/en-gb/library/ms181714.aspx</a>). In short if you add <code>OPTION (OPTIMIZE FOR (@myParameter = 'Some value that gives you a GOOD execution plan'))</code> after your <code>WHERE</code> and/or <code>ORDER BY</code> clauses it should fix the issue. Also, if you're wondering why when executing the same SQL in SSMS you always get fast results it's because SSMS has a default setting of ON for an option called ARITHABORT (<code>SET ARITHABORT ON</code>) which all other apps have set to OFF by default, but how it works and its implications are beyond my experience and I haven't bothered to read up on it. I have been told that I shouldn't use it though. I'm sure a real DBA can do a better job of explaining why.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POEntity Framework 4 Stored Procedure Call Timing Out
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USalimbada
UserOwnerUserId
1. USalimbada
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POEntity Framework 4 Stored Procedure Call Timing Out
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.