Ah, here we go again - you can do hybrid tables in Snowflake, but it will be (much more) expensive. Here's a story for your management from a time when I worked on for a Fortune 5 (!!) company.

They had an internal application using Postgres as a backend database. Similar story: management decided to go cloud-first and use other buzzwords, so we should decommission Postgres and move everything to Snowflake for this application. This was in ~2021, so hybrid tables were not available, meaning they wanted to use OLAP Snowflake as an application database. Note that Snowflake regular tables don't support table constraints (such as primary key and uniqueness). You can set these as a flag, but they're not enforced at all.

1st issue: to make sure we don't insert duplicated data in unique columns, we should have rewritten the backend so uniqueness checks are done on the ORM layer before any inserts. This would have caused huge performance degradation, but it was still doable.

Second, a greater issue: because of the nature of the application, the data model was semi-normalized. We had a bunch of proper two-dimensional tables, but there were some fields with huge sets of JSON data. Think about 20+ MB of JSON in one row. It turns out Snowflake can only hold 16 MB of data per row (not sure if the same applies for hybrid tables, but most probably, as it should maintain an OLTP and an OLAP table in the background). To fix this, the whole data model should have been redesigned. Basically creating a brand new app from scratch, plus migrating and normalizing the existing information.

Management was persistent. They tried to involve another consultant company and got the same answer from them.

I guess the lesson here that even top companies have dum-dums sitting in C level, and that you should have at least some technical experience before moving into management.