Subject: Clarification on SQL Mode Requirement for Custom Queries on GrowthBook Dear GrowthBook Team, I hope this message finds you well. I am writing on behalf of Sutara regarding an observation made while attempting to add a new custom query on the GrowthBook platform. During this process, our team noticed an option prompting us to “Switch to Legacy SQL.” A screenshot of this prompt has been attached for your reference. Can your team provide clarification on whether the use of Legacy SQL is a mandatory requirement for running custom queries on GrowthBook, or if queries written in Standard SQL are also supported. In the event that Legacy SQL is indeed required, we would like to explore the possibility of enabling support for Standard SQL queries for our organization, as it aligns better with our existing workflows and best practices.

Hi Sangram - it is not a requirement. Fact tables also support custom SQL, and are more efficient