Take control of your Databricks environment

Every data team has had this moment. Someone's poking around the Snowflake catalog and stumbles on a table with a name like staging_backup_v2_final or temp_export_q3. Nobody recognizes it. Nobody's sure who made it, what it was for, or whether anything downstream still quietly depends on it. So it stays. "We'll clean it up later" becomes the answer, and later, reliably, never comes. Multiply that moment by every...

Every team that turns on a cost automation asks some version of the same question first, even if they never say it out loud: will this come back to bite us? Suspending idle warehouses sounds great until the one time someone needed it and it wasn't there. Scaling down a multi-cluster warehouse sounds efficient until it means a report someone was waiting on took ten minutes longer than it used to. That hesitation isn't...

Snowflake World Tour lands in NYC on Thursday, October 15, and Seemore Data will be right there at booth 50 - ready to talk Snowflake cost, usage, performance, and everything in between. But here's the thing: why wait until the show floor to say hello? We'd love to start the conversation before October 15, so that by the time we're shaking hands at booth 50, we're already past the small talk and into the good stuff...

Ask most teams how they're tracking against their Snowflake contract, and you'll get a shrug dressed up as an answer. "I think we're okay." "Someone should check." "We'll know more at renewal." It's not that nobody cares, it's that "how much have we committed to, how much have we used, and where is that heading" turns out to be a surprisingly hard question to answer on demand, so it quietly stops getting asked until...

The best habits are the ones you don't have to remember to do. Nobody schedules a reminder to check their phone. It's just where attention already lives. Cost, usage, and performance awareness works the same way: it sticks when it shows up where a team already is, every day, not when it waits somewhere for someone to go find it. For most data and platform teams, that place is Slack. So that's where Seemore starts the...

Quick answer: We see this over and over: the costliest anomaly on a Snowflake bill is almost never a bad query. It's a good decision nobody walked back - a warehouse scaled up under pressure, then just… left. It's less a Snowflake problem than a human one: it's always easier to make an exception than to remember you made it. The fix isn't a better reminder. It's building the ending into the decision itself. Here's...