Periscope's SQL Views let the user define a table once that the whole team can use. By using the Periscope Data Cache add-on, users have the option to allow Periscope to optimize the view by keeping it materialized in the cache.
To get started, hover on the SQL Views menu in the header:
Click the "+" button and name the view.
The example here creates a view with all of the iOS Gameplays. This view will do the initial cleaning of the raw data:
The view is now available in the schema tab, where users can see what columns are available in the view:
When making the chart, anyone can select from the view like so:
SQL Views can be aliased by calling the syntax within the square brackets:
The new view will help count new iOS Gameplays over time:
All views are public to all write-access users regardless of whether or not it is published. However, as an indication to the team that the view is ready for public consumption, flip the "Published" switch at the top of the View:
This will put the View in the left-hand "Published" list. Everyone at the company sees the same list of Published Views.
For information on materializing SQL Views, check out the documentation here.
The number of rows returned in preview of a view's query results is limited to 5000 by default. This can be adjusted by either entering a new number into the Limit Rows text box, or by writing a LIMIT or TOP clause into a query.
If a LIMIT or TOP clause is defined in the query, the row limit defined in the UI will not be applied to the query. Limits that are defined in the query will apply to the view when referenced in other queries and if the view is being materialized. Row limits defined in the UI only apply to the preview of the view query, and are not used when the view is referenced in other queries or when the view is being materialized.
After the limit has been updated, the query will need to be re-run for the change to affect the results. If Limit Rows is unchecked, the preview query will run without a LIMIT or TOP clause applied to the query.