We finally got some time to I finally got some time properly reflect on everything @SnowflakeDB announced last week at Summit 2023.
Learn about every announcement and our thoughts on each in our latest post👇
select.dev/posts/summit-2…
Back in March we had the opportunity to speak at @datacouncilai in Austin. We had a blast sharing everything we've learned about @SnowflakeDB cost and performance optimization.
Slides & recording now available 👇
select.dev/posts/data-cou…
Another great post from @select_dev about CTEs.
Summary:
- continue using CTEs 🤘
- specify column names (don't "import" with select *)
- for special queries, experiment with repeating logic instead of reusing CTEs
- learn how to read query plan
select.dev/posts/should-y…
We're two weeks out from the next Analytics Engineering meetup in London at the @thoughtmachine office.
🙏Big thank you to our friends over @SpectaclesCI and @select_dev for letting us support such a great event!
The countdown to grab your seat is on! 👉 bit.ly/3Izk2hj
🗣️UK friends: The next Analytics Engineering meetup is approaching fast!
🤝We’ve joined forces with @SpectaclesCI and @select_dev in co-hosting this event at @thoughtmachine in London, March 23 at 6pm GMT.
Save your seat 👉bit.ly/3Izk2hj
@SnowflakeDB query tags are indeed awesome. We recently covered them in depth for those wondering why and how they should use them: select.dev/posts/snowflak…
Another great post from @select_dev about CTEs.
Summary:
- continue using CTEs 🤘
- specify column names (don't "import" with select *)
- for special queries, experiment with repeating logic instead of reusing CTEs
- learn how to read query plan
select.dev/posts/should-y…
⚠️ Unfortunately, this function isn't guaranteed to be deterministic. As a result, it won't be able to leverage Snowflake's result cache, so be careful when using in performance or cost sensitive applications where the query is executed frequently.
More generally, you can use these to find the row containing the min/max value for a particular column, then return the value of another column in that row.
In @SnowflakeDB 's latest release, they've given us a nice new set of aggregate functions: min_by and max_by.
In this example I look across each user's query history, and find the ID of the first and last queries they executed.
Range joins are notoriously slow in many databases. @SnowflakeDB is no exception. We're using a binned range join technique across a number of models in our @getdbt project and have seen incredible results. A 300x speedup for this query.
4K Followers 2K FollowingEngineering Manager, AI Data Products at @justbobsledit. Formerly led Data and Engineering at @thebeatapp , @omioglobal , @thoughtworks .
4K Followers 987 Followingco-founder and CEO of Hex (https://t.co/hbgguInF1h / @_hex_tech) - former @PalantirTech @formationbio - personal site: https://t.co/c38nDG5Dfl
293 Followers 832 FollowingGlobal VP of FDE Delivery @doitint.
Ex @CheckPointSW, Ex @algolia
Blog: https://t.co/G6VydfVdwm
My teams blog: https://t.co/OPAF9kURwc
284 Followers 2K FollowingI was born the day Len Bias died. Journalist turned analyst turned software engineer. Patiently awaiting the final Robert Caro LBJ book.
3K Followers 2K Followinggeek dad with a clipboard
founder @ Katabase and Great Expectations
operating advisor @ Bessemer VP
data, ai, startups, dev tools, systems thinking
storytel