u/Key_Card7466

Just to clarify — I was pulled into the BG call by Ojas since my name was mentioned for the Horizon Catalog demo, so I went ahead and presented what we had so far.

Given I’m mostly aligned to Vibe Analytics right now, just wanted to check how much I should continue supporting BG going ahead. Happy to help within limits, but would prefer clarity on this.

My tech lead mentioned my name for the work and now she is messaging that I should have mentioned that I am busy with other project and my maximum bandwidth is on another project. She messaged -

I won't be able to guide you on that .. so please respond accordingly to ben

For demo, it's enough what we done so far

What diplomatic answer should I give to her please reply fast to her and ben. For ven it could begin as discussed with my team lead we are currently focusing on Also, as discussed, for the next steps I’ll keep the demo limited to the current scope and reach out if any support is needed.

Hey folks,

I’m currently working on a proposal presentation and could use some real advice from people who’ve actually built data governance setups.

The situation is roughly this: They’re on Snowflake as their main data platform, and they’ve already built a small internal tool using Streamlit. It’s pretty basic/static right now.

They’re not interested in bringing in heavy tools like Collibra or Alation, so the expectation is to keep things lightweight but still useful.

What we’re trying to cover:

Data ownership / stewardship Some level of catalog/discovery Basic lineage (nothing too fancy)

My current thinking is: Use Snowflake as the base (metadata, tags, etc.), and build a thin layer on top (probably Streamlit) for visibility and interaction. Maybe add some light automation later for tagging or data quality.

Where I’m unsure / would love input:

How are people practically storing and managing things like owners/stewards? Just metadata tables in Snowflake? For a “lightweight” setup, how much lineage is actually worth building before it becomes overkill?

Any framework/resources/YT video/sources/LinkedIn Post would really be helpful .

Thanking in advance!

Hey folks,

I’m currently working on a proposal presentation and could use some real advice from people who’ve actually built data governance setups.

The situation is roughly this: They’re on Snowflake as their main data platform, and they’ve already built a small internal tool using Streamlit. It’s pretty basic/static right now.

They’re not interested in bringing in heavy tools like Collibra or Alation, so the expectation is to keep things lightweight but still useful.

What we’re trying to cover:

Data ownership / stewardship Some level of catalog/discovery Basic lineage (nothing too fancy)

My current thinking is: Use Snowflake as the base (metadata, tags, etc.), and build a thin layer on top (probably Streamlit) for visibility and interaction. Maybe add some light automation later for tagging or data quality.

Where I’m unsure / would love input:

How are people practically storing and managing things like owners/stewards? Just metadata tables in Snowflake? For a “lightweight” setup, how much lineage is actually worth building before it becomes overkill?

Any framework/resources/YT video/sources/LinkedIn Post would really be helpful .

Thanking in advance!

What real-world use cases or extensions can I build open on Sensitive Data Classification & Policy Enforcement in snowflake to experimenting and building something impactful

To run SYSTEM$CLASSIFY across -schemas to detect PII (emails, SSNs, phon e numbers), then auto-generate and apply masking and row access policies based on the results. Policies are tied to tags so new columns are automatically p rotected-building a governance-as-code layer for GDPR/CCPA compliance.

I’m still in the exploration/ideation phase, so open to experimenting and building something impactful in Snowflake.

Would really appreciate your inputs 🙌

Thanks in advance!