
He/Him. DBA. Automation. Food, Coffee, Whiskey (not necessarily in that order)... @SOZDBA@techhub.social
Ireland
Joined February 2009
- Tweets9.8K
- Following2.1K
- Followers1.4K
- Likes20.2K
Hopping back on here to say:
@MattMcgiffen ... TDE... thank you 🙏 – at Limerick, Ireland
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… – at Limerick, Ireland
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.
My #tsql2sday post is up just before the deadline:
nocolumnname.blog/2023/07/11…
Thanks for hosting @erikdarlingdata
#sqlblog
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
Thanks to all at #DataCeili. Sorry, I have to head off early, but I'm looking forward to catching up with you all again! – at Dublin City, Ireland
🙌🙌
Dbatools FTW with replication
@sql_williamd #dataceili
#dataceili kicking off with Partitioning – at Dublin City, Ireland
#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? 😇😈
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
cc @jodouglass 😇
Replying to @PAH66
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








