This message was deleted.
# secoda-support
w
This message was deleted.
e
Hey Benoit, which integration type is the profiling failing for? Also there currently isn’t a way to profile all tables. The reason why we chose this is because it’s fairly compute intensive and we didn’t want to increase people’s compute bills. However, we can add a button in the data settings to run the profiler on all columns and just warn people about the query it’ll be running against all the columns.
k
Bigquery (or maybe dbt) integration
it’s failing for any table really. It worked fine the first time I tried the feature but since then I have been unable to use it on another table
e
Ah that explains it, we’re trying to profile with the dialect “dbt” instead of bigquery. I’ll push out a quick fix for this.