AFAIK bundles don't have a way of generating sql scripts with the Jinja variables (maybe this could be a feature?), so you will have to deploy and run your code in Databricks to find out if the jinja ...

I learned from our Databricks reps that each individual SQL command run in the Databricks SQL UI is generated against a separate SparkSQL environment. Metadata Metadata. Assignees. No one assigned.

All tests used 20-node clusters with Ubuntu 18.04.1, kernel version 5.4.0-1059-AWS, Databricks 9.0, Apache Spark 3.1.2, Scala 2.12. Both instance types had 8 vCPUs and 64GB RAM.