Extended Events are notorious for being poorly documented. Duration / units is especially so, see:
Extended event duration Millisecond or Microsecond?
Despite the fact that "seconds" is in the event field name, you're correct that the value being reported is nowhere near seconds. You menti...
Three suggestions: (1) stop using the deprecated sys.sysprocesses (2) use the ANSI standard <> instead of != (3) stop reinventing the wheel and writing these homemade queries from scratch and having to re-solve the same issues others before you have already solved - go grab Adam Machanic's sp_whoisactive, Brent Ozar Unlimited's First Responder Kit, or Glenn Berry's DMV queries. They're all great but when you're up for big kid monitoring tools, let me know. :-) — Aaron Bertrand ♦2 hours ago
> As its name implies, Regular Resource Semaphore is used by all queries under normal condition, while Small Resource Semaphore is used by small size queries (less than 5 MB)
@sp_BlitzErik So, are you really seeing multiple queries destined for the small semaphore blocking the large? It's quite possible there is a slack factor involved, to avoid one type dominating, which would be quite ironic.
I have started looking in MERGE as an option that I would use in my Application to process transactions INSERT/UPDATE. Seems that a lot of SQL experts are recommending this approach. However, while exploring this method I found some common problems that MERGE can cause. Here is the link from one ...
As someone who is so new a new contributor, I should let you all know that I had never heard of compilation / memory grant gateways, and that the discussion and links about them here have been really interesting to me!
Hey @PaulWhite - there's a broken image in this blog post. Looks like it used to be in the msdn page you linked to, but the corresponding MS docs page doesn't have any images at all.
Just thought I'd let you know in case you know of some other source for that image.
> i.msdn.microsoft.com normally uses encryption to protect your information. When Google Chrome tried to connect to i.msdn.microsoft.com this time, the website sent back unusual and incorrect credentials.
/*
We estimate that implementing the
following index could improve query cost (1511.44)
by 60.0274% for 4 executions of the query and 100.963 rebinds of the spool per execution over the last 3 hours.
*/
We are considering an insert-only approach for this potential columnstore table - so the thing it represents is "immutable" and each time the form is saved, a new copy (row) is created. Helps us track workflow / history among other things. Does that seem like a reasonable use case?
We estimate that implementing the following index could reduce the estimated query cost (currently 1511.44) by 60.0274%. There were 4 executions of the query over the last 3 hours. Adding the index will eliminate 100.963 spool rebinds per execution.
@sp_BlitzErik thank you for your help, if you answer explaining why I won't find SHRINK I will accept your answer. — James Jenkins4 mins ago
Mikael Eriksson did that to me yesterday. Answered over six or so comments. Then added an answer, deleted comments, but left the other side of the conversation. Someone get me my medicine.
@PaulWhite Oh really? I didn't know that. I've not really read up on how Hekaton works behind the scenes (although I've considered buying Kalen's book on the subject).
> Thanks for leaving a comment! Increasing the comment:question ratio improves a site's Stack Exchange Welcomingness Rating (SEWR). A high SEWR assures a site will not be shut down due to unhappy Twitter posts.
I have a table that contains 80+ sparse columns along with a column set column, this is a brief example:
DROP TABLE IF EXISTS #ColumnSet
GO
CREATE TABLE #ColumnSet
(
Id INT NOT NULL
, Value1 VARCHAR(100) SPARSE NULL
, Value2 VARCHAR(100) SPARSE NULL
, Value3 ...