Right now there is a gap in the product if you are using Snowflake in (Horizon) Rules and/or Data Designer.
In order to allow Snowflake Schemas as a source for either of those two areas of the product, you need to set up a per Schema connection in Connectors 2.0. Their usage in rules don’t show up as “Jobs” either, so it’s not as simple as checking job dependency either.
If you want to remove one of those connections (as of this writing you are limited to 5) there is no way in the product to validate where that connection is being used.
Even if you have a robust naming scheme to identify any Data Design and Horizon Rule using a Snowflake Schema in one of the tasks, you still have to manually go into each asset to see which one is being used (again, there are ways to mitigate this outside of the product with copious documentation but the only true answer is what the platform registers).
I am aware that in Data Management Dependencies there is a “Connectors” application you can select (there’s also Salesforce and Dynamics Connects specifically called out, but not for Snowflake) but that also would still require you to go through every object, and not really solve the issue either.
There are a few ways that immediately come to mind to make this easier for admins to review at scale:
- Update Analyzer and include Snowflake connection usage, by connection
- In Rules Engine, include Snowflake Connections/schemas as filter options (e.g. Source Object filters)
- As Data Designer and Rules engine are getting more and more similar, there’s no reason why similar filters for source, created by, etc., can’t be added to Data Designer as well. Those updates should also include Snowflake as a selectable option. (Getting those filters in DD in general might be its own request)
This is also very Snowflake specific, but this idea can be expanded to other types of connections as well
This would help organizations manage dependencies and have a much better grasp of external data usage and dependencies within Gainsight.
