Hey team, how have you been? I hope you're all doi...
# ask-questions
d
Hey team, how have you been? I hope you're all doing well. I got involved in a project in which our client wants to run an experimentation program using GrowthBook. I have not much experience running the tool but I'm eager to learn more. After some back and forth, I have a few questions, that hopefully are not too dumb. 1. Write Permissions: GrowthBook doesn't write anything to the client's warehouse, right? I'm asking because it seems they created an empty table to be used as a "FACT TABLE" inside their Databricks environment. 2. Fact Table Definition: My understanding is that the Fact Table should actually be a SELECT query pointing to the client's existing raw events data (e.g., from Segment or Snowplow), not a new table created specifically for GrowthBook. Is that correct? 3. Databricks Permissions: Our current Access Token connection is "Connected," but the SQL Explorer shows "No tables found." Does this confirm that the token is missing
SHOW
and `USAGE`/`SELECT` permissions on the necessary Catalogs/Schemas, even if the basic connection works? Any guidance on these points would be hugely appreciated as we finalize the Databricks setup! Thanks a lot!
s
Hi Robson 👋 1. Right. GrowthBook doesn't write to your warehouse, with an exception for pipeline mode/incremental refresh, which may write temp tables to improve performance. This requires explicit permissions to be set (and not available 2. Yep, Fact Tables are defined by a SQL select statement as you've described it. 3. Yes, you seem to be right about the permissions error. I'd begin by confirming that the access token has permissions to execute sql queries against your warehouse. More info here: https://docs.growthbook.io/warehouses/databricks
d
Hi Ryan, Thank you so much for your reply. Your explanation makes perfect sense and I finally see the light at the end of the tunnel. I'll focus tomorrow on fixing the access token permissions on the Databricks side and hopefully it'll finally work properly. Thanks again for your quick and helpful response!