SELECT video_content FROM LIBRARY WHERE SLUG='qa-pros-and-cons-of-defining-a-semantic-layer-in-count-metrics-vs-dbt'
Q&A - Pros and cons of defining a semantic layer in Count Metrics vs dbt
Loading video player...
That's a good question. So the count metrics catalog brings you a lot of pros that you won't get from DBT. So for example, we bring you our caching, which lets you actually move your data onto our server. Once your data is on our server, the performance payoff is huge. So you're gonna see all of the time that is usually spent extracting data from your system onto ours is now gone because it's already on our system. The other thing that caching lets you do is set up a schedule so that you can actually protect how often your analysts are hitting your source system. So by setting up caching, you could say, like, only run this at six AM every day, and then hold it on the account server for twenty four hours. And what will happen is it will run the query on your data platform at six AM once, and then for the rest of those twenty four hours, everyone that uses the catalog is only hitting our server. So your connected source platform is gonna experience a a boost in any bandwidth. It's also gonna see a cost reduction in the number of queries run on it. I guess the other main benefits of running these building your semantic layer in account catalog is that with the incoming AI agents, you're gonna have a robust foundation for them to deliver maximum value to you.