...
In the defining SQL of a materialized view, you can use any supported Synapse SQL you can use in a query, as well as the following operations:
...
sepallength | sepalwidth | petallength | petalwidth | species | Common NamecommonName |
|---|---|---|---|---|---|
5.1 | 3.5 | 1.4 | 0.2 | Setosa | bristle-pointed iris |
4.9 | 3.0 | 1.4 | 0.2 | Setosa | bristle-pointed iris |
7.0 | 3.2 | 4.7 | 1.4 | Versicolor | blue flag |
6.4 | 3.2 | 4.5 | 1.5 | Versicolor | blue flag |
6.3 | 3.3 | 6.0 | 2.5 | Virginica | Virginia blueflag |
5.8 | 2.7 | 5.1 | 1.9 | Virginica | Virginia blueflag |
...
If we create two separate Synapse tables for the Iris dataset (syn51941633) and the mapping between species and column common name (syn51941637), we can create a new materialized view with the following defining SQL:
...
To query a materialized view, a Synapse user must have “download” permission on all source tables (if any exist). Additionally, rows that are derived from views will only be each row in a materialized view that is derived from a row in a view is only visible to Synapse users that have view permission of all of on the corresponding original files that were used to populate the source viewobject, such as a file. Rows that are derived from multiple objects in one or more views are only visible if the user has view permission on all referenced objects.