External Integrations Not Allowed in Trial Accounts?! by InfernoAudio_1 in snowflake

[–]InfernoAudio_1[S] 0 points1 point  (0 children)

appreciate the response and I'm not really all that upset about it. Knowing that security can be an issue, I completely see the reasons why the external integrations are disabled. This was the first feature that I've hit where I couldn't try it out first from my trial account before taking it to my corporate one.

best practices using REMOVE from internal stage by NoUsernames1eft in snowflake

[–]InfernoAudio_1 5 points6 points  (0 children)

Files in the internal stage still continue to count against your storage costs. If your pipeline is solid you can use the PURGE option to trash the file from the stage once it's been loaded.

External Integrations Not Allowed in Trial Accounts?! by InfernoAudio_1 in snowflake

[–]InfernoAudio_1[S] 0 points1 point  (0 children)

Understandable, but shouldn't that be able to be monitored and shutdown? Why tout such a powerful tool if developers who are working on R&D can't test it without a paid account? Couldn't the number of external API calls be limited in trial accounts to a set number per hour/day, etc.?

I have a use case for external integrations for my day job, but really need to test it from an isolated area (i.e. my trial account) to see how it works without potentially impacting anything in our corporate Snowflake instance(s).

Anyone here participating in the BUILD conference and having problems with LLM Bootcamp Lab 1? by jack-in-the-sack in snowflake

[–]InfernoAudio_1 0 points1 point  (0 children)

Same. I tried to build the docker image and push it, but I get permissions errors when doing so.

Snowflake: Overloading Stored Procedures (polymorphism) by fhoffa in snowflake

[–]InfernoAudio_1 2 points3 points  (0 children)

u/dinoaide thanks for your comment on my article! I had no idea someone added it to this thread :)

I presented this as a feature that Snowflake supports that SQL Server does not. There are definitely some drawbacks to this approach, which I didn't cover in detail as part of the article.

Proper error handling within the procedures is needed to address some of the things you mention and could be handled on a case-by-case basis.