Joined February 2009
- Tweets 9,836
- Following 2,162
- Followers 1,426
- Likes 20,376
1,170 Photos and videos
1 Dec 2023
Dice and Desire โ I enjoyed every one of the 790 minutes I spent with you in 2023. Thank you. #SpotifyWrapped
open.spotify.com/show/2TL45Rโฆ
101
22 Nov 2023
Based on the number of connection requests I received today and yesterday, I assume people are talking during the PASS Summit.
I can only say thank you; the stories are grossly overestimated in my favour.
8
673
10 Oct 2023
4
191
11 Jul 2023
My #tsql2sday post is up just before the deadline:
nocolumnname.blog/2023/07/11โฆ
Thanks for hosting @erikdarlingdata
#sqlblog
1
2
566
30 Jun 2023
I've decided to highlight blog posts that have helped me out when they help me out.
Rather than just read, action, then forget.
So thank you @Kendra_Little for your post on "NO_PLAN and NO_INDEX: Breaking a Forced Query Store Plan"
littlekendra.com/2016/03/25/โฆ
#SQLServer
3
256
9 Jun 2023
Thanks to all at #DataCeili. Sorry, I have to head off early, but I'm looking forward to catching up with you all again!
2
133
9 Jun 2023
5
124
11 Apr 2023
4
298
9 Mar 2023
#SQLServer challenge for anyone who likes figuring things out.
I've created the index it asked me to.
Run the query again, and it suggests the same index
**even though it uses it**
I can replicate but I can't figure out why.
Anyone want to try to replicate it? ๐๐
5
1
2
950
10 Mar 2023
Not sure if this is a hint, but the issue is only present when the query goes through Full Optimization.
When it's Trivial Optimization, no missing index shows, and the query uses the index fine.
That's why I had to add
AND (SELECT 1) = (SELECT 1);
to the WHERE clause
1
167
10 Mar 2023
Final trick, and thanks to those that responded, I now know more than before.
I can only replicate this with these conditions:
1. FULL optimization
2. Range comparison on 1 of the columns,
3. Partitioned table (Yes, I was sneaky and didn't mention this)
122
10 Mar 2023
cc @jodouglass ๐
10 Mar 2023
Thankfully it's a small enough index that I can try all the different orderings.
All of them lead to the same "use this index" and all the recommended indexes come back as the same column1-created_date-column2 order
So, index column order doesn't seem to matter so far
299