LOCKING FOR ACCESS

Some parts in the output code are omitted for clarity reasons.

Non-relevant statement.

Notice that this statement is removed from the migration because it is a non-relevant syntax. It means that it is not required in Snowflake.

Description

The functionality of locking a row in Teradata is related to the access and the privileges. Revire the following documentation to know more.

Sample Source Patterns

Locking row

Notice that in this example the LOCKING ROW FOR ACCESS has been deleted. This is because Snowflake handles accesses with roles and privileges. The statement is not required.

Teradata

IN -> Teradata_01.sql

REPLACE VIEW SCHEMA2.VIEW1
AS 
LOCKING ROW FOR ACCESS
SELECT * FROM SCHEMA1.TABLE1;

Snowflake

OUT -> Teradata_01.sql

--** SSC-FDM-0007 - MISSING DEPENDENT OBJECT "SCHEMA1.TABLE1" **
CREATE OR REPLACE VIEW SCHEMA2.VIEW1
COMMENT = '{"origin":"sf_sc","name":"snowconvert","version":{"major":1, "minor":0},{"attributes":{"component":"teradata"}}'
AS
--** SSC-FDM-0001 - VIEWS SELECTING ALL COLUMNS FROM A SINGLE TABLE ARE NOT REQUIRED IN SNOWFLAKE AND MAY IMPACT PERFORMANCE. **
SELECT
* FROM
SCHEMA1.TABLE1;

Known Issues

No issues were found.

Related EWIs

1. SSC-FDM-0001: Views selecting all columns from a single table are not required in Snowflake.

2. SSC-FDM-0007: Element with missing dependencies.