Ah, very interesting Gail! Thanks for that additional info.

So, just to double check, when you run the second INSERT after the TRUNCATE (all within the same transaction) in 2012 SP2,...

Ah, now it's getting really interesting, since this seems to be a distinct phenomenon.

For that bit of code, I'm seeing the same as you two. On 2008 R2 SP3, page...

I know what lock escalation is, but thanks for the refresher 🙂

Technically it does rely on changing modes (IS to S and IX to X) at the table level, and...

I didn't say it was blocked; I said lock escalation failed, because it seems the engine can't escalate to X from Sch-M (because Sch-M is a more protective lock).

Very different...

Ah, it took me a few reads, but I think I understand what you're saying now.

If I understand you correctly, your point is that even in the "fixed" version,...

Thanks for pointing out that article Gail!

From Microsoft's response in the Connect item Adam mentioned:

Adam: This is a regression in lock escalation algorithm in SQL2008. We know what...

I'm glad I could help!

We've all been there. 🙂

Cheers!

If I understand what you want, you don't need to partition the result, since you want the number sequence to persist across all the values, based solely on ColB.

At least...

Heh, I really hope mirroring doesn't go away for a long, long time. AGs, for all their...

Off the top of my head, the most straightforward way to do that is probably to check all the databases in which the sessions have locks. Something like this:

SELECT request_session_id,...

Based on the Excel sheet it looks like what you're doing is getting the the percentile rank of the volume for day 1 for each symbol, basing that percentile rank...

If I understand your requirement correctly, then the below should do the trick, convoluted though it is:

WHERE  EXISTS (

    SELECT *

    FROM User_Activities AS ua

    WHERE p.Id...

Ah, now...

ASYNC_NETWORK_IO waits are rather unfortunately named. They don't necessarily indicate that the network is the bottleneck. Basically, when a client issues a query, SQL Server places the result set to...

No. The information in sys.dm_db_index_usage_stats will persist after a reorganization. A rebuild will remove the entry for that index in sys.dm_db_index_usage_stats, and then stats collection will start over.

Cheers!