Databrain’s Custom SQL Revamp: A Cleaner, Smarter Way to Query

SQL is the language of data. It’s powerful, flexible, and the backbone of countless insights. But let's be honest—writing isn't always a walk in the park. Juggling complex joins, hunting for that one misplaced comma, and trying to decipher cryptic error messages can turn a quick query into a lengthy debugging session.

We believe that building with data should be intuitive and inspiring, not frustrating. That’s why we went back to the drawing board with our Custom SQL interface. Today, we're thrilled to introduce a completely revamped experience designed to make your query-building process faster, smarter, and a whole lot smoother.

The Foundation for What's Next

This revamp is more than just an upgrade; it's a critical foundation for the future of SQL in Databrain. We're laying the groundwork for an AI-SQL editor/copilot that will truly transform how analysts and business users interact with SQL. Imagine a system that not only helps you write queries but also understands your intent, suggests optimizations, and even helps generate complex logic.

Beyond AI, we're also planning to integrate advanced features like data lineage to provide a clear understanding of your data's journey, and dbt transformations to streamline your data modeling workflows. This comprehensive approach will ensure that Databrain remains at the forefront of data analysis, providing tools that are not just powerful but also intelligently assist you every step of the way.

From Guesswork to Guidance: What We Set Out to Solve

If you’ve spent any time writing SQL in Databrain, you know the old interface got the job done—but it didn’t always make things easy. Editing could feel cramped. Error messages sometimes left you scratching your head. Saving a query for later? That wasn’t always as seamless as it should be.
We wanted to fix that. So, we went back to the drawing board and rebuilt our Custom SQL editor with a focus on clarity, feedback, and flexibility.

Our goal was to create an experience that feels less like a test and more like a conversation with your data, with a helpful co-pilot guiding you along the way.

Meet the New Custom SQL Experience

The new interface is a breath of fresh air, designed with two core principles in mind: clarity and confidence.

• A Focused, Clean Editor: The first thing you'll notice is the clean, uncluttered space. We've stripped away the noise so you can focus on what matters: your code. The improved layout gives you a more organized and comfortable environment to build, test, and refine your queries, no matter how complex.
• Validation That Actually Helps: This is where the magic happens. We've moved beyond simple "pass/fail" error messages. Our new validation system works with you in real-time, highlighting potential issues as you type. Misspelled a column name? It’ll let you know. Missing a join condition? You’ll get a helpful prompt. It’s designed to catch errors early and provide clear, actionable feedback so you can fix them instantly, not after a failed run.

Beyond the Query: New Ways to Bring Your Data to Life

Getting the right data is only half the battle. Presenting it in a useful way is just as important. With the SQL revamp, you now have powerful new options for what happens after your query runs successfully.

When you're ready to save your work, you can now transform your results into:

• Table Chart: The classic, clean table you know and love. It’s the perfect way to present raw, structured data for detailed review.
• Table Chart with Dynamic Table: Take your tables to the next level. This option turns your static results into an interactive playground for your end-users, allowing them to sort, filter, and explore the data directly within the chart.
• New Chart: Why stop at a table? Instantly pivot your query results into a bar chart, line graph, or any other visualization. This is the fastest way to go from raw numbers to a compelling visual story without any extra steps.
• Custom Dataset: This is the real game-changer. You can now save the output of any query as a new, reusable Custom Dataset within Databrain. This allows you to create a "single source of truth" from a complex query that your entire team can then use to build other charts and dashboards. It saves time, reduces redundant work, and ensures everyone is building from the same, standardized data.

It's Live Now—Go Take It for a Spin!

The enhanced Custom SQL interface is now available for all users. Just head to the Custom SQL editor to start your next query and experience the difference.

We built this for you, and we can’t wait to see what you build with it. Dive in, give it a try, and let us know what you think. Happy querying!

Frequently Asked Questions

What happens to my old queries? Will they still work?
Absolutely. All your existing saved queries are safe and will continue to work just as they did before. You can open any of them in the new editor to take advantage of the enhanced validation and new saving options.

What kind of SQL can I write in the new editor?
The interface supports all the standard SQL you're used to, including complex joins, subqueries, GROUP BY, and window functions. The improved validation is designed to help you with all of them.

How do I turn my query into a bar chart?
Once your query runs successfully, just click "Save." You'll see an option to save it as a "New Chart." From there, you can choose the visualization type you want, like a bar chart, and configure it as needed.

Can my teammates use the Custom Datasets I create?
Yes! That’s one of the best parts. When you save a query as a Custom Dataset, it becomes a shareable resource in your workspace. Your whole team can then use it as a starting point for their own analyses, ensuring everyone is on the same page.

What if I make a mistake in my query? How does the new validation help?
The new validation system provides instant feedback right in the editor. It will highlight the part of your query that has an issue and provide a clear, easy-to-understand message about what's wrong and how you might fix it. No more vague "syntax error" messages.