by Brandon Carver, on Jun 30, 2022 3:00:00 AM
However, when converting SQL procedures in a source platform to SQL procedures in Snowflake (Snowflake Scripting), the conversions are much more straightforward. Let's take a look at what this looks like with a very simple example in Oracle PL/SQL.
Let's take a sample procedure with a RAISE statement as an example. (Note that you can use this code to try this out.) Here's what that could look like in Oracle.
Snowflake SQL Procedure (Snowflake Scripting)
In Snowflake Scripting, the same procedure would look like the following:
Looks... pretty similar to the first one, right? That's because it is. The RAISE function implemented in Snowflake with Snowflake Scripting is essentially the same as the function the RAISE function in Oracle. That's by design. SQL has been around longer than Snowflake, and now that Snowflake Scripting is here, Snowflake's implementation of procedures written in SQL will look similar to what's already out there. The output code in Snowflake Scripting is easy to understand and easy to manipulate for developers familiar with SQL.
So... time for a decision?
Unless it's about that whole coffee or tea thing. That debate continues to rage around the mahogany halls of the Mobilize.Net offices and shows no end in sight.