Band Join
Last updated
Last updated
A band join is a special type of nonequijoin in which key values in one data set must fall within the specified range (“band”) of the second data set. The same table can serve as both the first and second data sets. ()
In this section, we will see how a band join is executed in Snowflake and the execution plan is very similar to the improved version of Oracle.
If you migrate this code without the create tables, the converter won’t be able to load semantic information of the columns and a warning will appear on the arithmetic operations.
The results are the same making the BAND JOIN functional equivalent.
As extra information, the special thing about the band joins is the execution plan.
And in the following image, we will see the execution plan in Snowflake:
The query result will have the same content in both database engines but the order might be different if no Order By clause is defined in the query.
Migrating some SELECT
statements without the corresponding tables could generate the : Types resolution issues. To avoid this warning, include the CREATE TABLE
inside the file.
The following image shows the (implemented since Oracle 12c) for the test query:
Types resolution issues, the arithmetic operation may not behave correctly between string and date.