There really isn't a direct mechanism from extended events to capture tempdb use by a given query, procedure or function.

While you could do what you've already done through the DMVs,...

When an INSERT occurs, a lot of locks are taken out. It's not just a question of adding a row at the end of the last page (assuming a clustered...

So that requires that you have distinct logins, OR, that everyone logs in and uses the application value on the connection string. Then, you can filter based on the login,...

There it is.

Every non-clustered index includes the key for the clustered index (or, an ID for a heap) so that from the non-clustered index, you can get to the appropriate...

[RSSQLDB].[dbo].[RSINVOICE].[DraftNum]=[@DraftNum]

DraftNum is in that index somewhere. It's a key, an include column, or as Frederico says, part of the clustered index key. Above is from the predicate of the index...

I like the idea of splitting the identity keys, artificial keys, from the natural keys. I also like the idea of hiding the artificial keys from the end users. I'm...

Absolutely ROWLOCK is going to cause blocking. In fact, using the ROWLOCK hint may even cause more blocking. Hints are not hints. Hints are commandments that the optimizer and query...

Thanks for posting that you found the answer. That'll prove helpful for the person who searches for the same issue and finds your original post.

I'm sorry, but you're going to have to supply a bit more detail. That screen shot shows nothing at all. What is it you're trying to do. What specific errors...

A Constant Scan is basically adding a column to the data being passed around. Look at the properties and it will define what it is adding. It may be something...

Or, don't rebuild the indexes at all. Find a good fill factor, set that, and leave them alone. Just maintain statistics.

Different rules for columnstore indexes though.

Or, don't rebuild the indexes at all. Find a good fill factor, set that, and leave them alone. Just maintain statistics.

Different rules for columnstore indexes though.

Strong recommendation: work backwards.

Figure out what it is that you need to deliver. Then, get a set of scripts together to deliver it, that doesn't involve using a cursor. That's...

I'm sorry, but I don't recall 2019 being a big mess. Most of the people I know who upgraded to it were happy. Were there issues? Sure. As with anything....

Probably not. Data modifications have to go somewhere to be persisted. That's locally. As the amount of data you modify grows, more and more data is stored locally. Now, you...