increase your dbt thread count, you should
Thanks for sharing!
Wrote about this in more detail here for those curious: select.dev/posts/snowflake-d…
SELECT retweeted
SELECT Cloud、3ヶ月ほど運用したので満を持して、事例公開しました。
OSS版も素晴らしいですが、Cloudはもっとすごいので、Snowflakeのコストやパフォーマンスで、お困りの方は、是非チェックしてください🥰
@SnowflakeDB_jp @SnowflakeDB @select_dev
❄ SELECT Cloud国内初導入!❄
Snowflake使用コストを最大40%最適化
SELECT Cloudについて @pei0804
が導入実績を解説!
> 利用料を40%程度削減できてるワークロードも出てきて、この節約機能だけで、SELECT Cloudの利用料を回収できてしまうレベルのインパクトでした。
techblog.cartaholdings.co.jp…
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-2023
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-counci…
SELECT retweeted
Geeking out about Snowflake optimization with the @select_dev crew @NiallWoodward and @ianwhitestone. 5/7
SELECT retweeted
New @dbt_labs Analytics Engineering Podcast is LIVE🎙️! @jthandy and I sit down with @brad_culberson from @SnowflakeDB and @NiallWoodward from @select_dev to talk about cloud warehouse optimization. Listen for practical advise on a top of mind topic 🧠🫰
open.spotify.com/episode/2j8…
Was about to tweet our latest post but @toppare bet me to it 🏃♂️. Thanks for sharing!
Curious about when to use CTEs in Snowflake? Read on!
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-you-…
SELECT retweeted
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
SELECT retweeted
🗣️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
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.
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.
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.
As of Tuesday, users now have programatic access to all the query performance statistics available in the Query Profile. This is possible through a brand new function, get_query_operator_stats. You can run this function on one query_id at a time:
Similar to the Query Profile, data is only retained for queries run in the last 14 days. If you want this to stick around for longer, you’ll have to persist it with a scheduled Snowflake job.
We'll be diving deeper into this functionality and sharing some sample queries in the coming weeks. For now, you can read the:
- Original announcement post: snowflake.com/blog/programma…
- Snowflake docs: docs.snowflake.com/en/sql-re…
- Our post on the Query Profile: select.dev/posts/snowflake-q…













