Marking a Table or View for Data Permissions

When creating a permission to make your Analytics Environment data available to a partner to use in their Analytics Environment, you should typically only give your partner access to a portion of the main table populated by your data feed, such as the following approaches:

A BigQuery table rows contain individual records and columns organize each row's information into fields.

Every table is defined by a schema that describes the column names, the data types, and other information. You can specify the schema of a table when it is created. Alternatively, create a table without a schema and then declare a schema in the query job or load job that first populates it with data.

A view is a virtual table defined by a SQL query. When you create a view, you query it in the same way you query a table. When a user queries the view, the query results only contain data from the tables and fields specified in the query that defines the view.

A table is a "static" connection to a table (the table will not update along with the transaction table) unless you did further engineering work to ensure the new table will update. A view is a "live" connection because it references the original table that is being updated by the data feed.

The performance of tables and views may differ. A view is a query, so if you write a complex query to populate the view and then write another complex query to query the view, performance might be negatively impacted.

A table is simpler: you just query the object directly. So if you write a complex query, there's no additional complexity added by the object because it is already defined in itself.