SnowConvert AI - SQL Server-Azure Synapse - Views¶
Applies to
SQL Server
Azure Synapse Analytics
Note
Some parts in the output code are omitted for clarity reasons.
In this section, we will check the transformation for the create view.
Sample Source Patterns¶
SIMPLE CREATE VIEW¶
The following example shows a transformation for a simple CREATE VIEW statement.
Transact¶
Snowflake¶
CREATE OR ALTER VIEW¶
The CREATE OR ALTER definition used in SQL Server is transformed to CREATE OR REPLACE in Snowflake.
Transact¶
Snowflake¶
CREATE VIEW WITH¶
In this type of View, after the name of the View, the following clauses can come
WITH ENCRYPTIONWITH SCHEMABINDINGWITH VIEW_METADATA
Warning
Notice that the above clauses are removed from the translation. because they are not relevant in Snowflake syntax.
Transact¶
Snowflake¶
CREATE VIEW AS SELECT WITH CHECK OPTION¶
In this type of View, the clause WITH CHECK OPTION comes after the end of the Select statement used in the Create View.
Warning
Notice that WITH CHECK OPTIONis removed from the translation, because is not relevant in Snowflake syntax.
Transact¶
Snowflake¶
CREATE VIEW AS COMMON TABLE EXPRESSION¶
Common Table Expressions must be used to retrieve the data:
Transact¶
Snowflake¶
UNSUPPORTED SCENARIOS¶
Common table expressions with Update, Insert or Delete statements will be commented out because they are not supported in Snowflake and SQLServer.
In the case where an invalid CTE is added to the view, this will be completely commented out.
FINAL SAMPLE¶
Let’s see a final sample, let’s put together all the cases that we have seen so far and see how the transformation would be
Transact¶
Snowflake¶
As you can see, we changed the OR ALTER with OR REPLACE and we removed the clause WITH ENCRYPTION that comes after the view name and the WITH CHECK OPTION that comes after the Select.