Run a query with SQL Data Explorer
SQL is a programming language used to communicate with databases. A basic understanding of writing SQL queries is required to use SQL Data Explorer. See our collection of "recipes" in the SQL cookbook. Queries are run against Snowflake, so use the Snowflake SQL dialect. Note that non-SELECT
statements and $SYSTEM
commands are limited in functionality.
When you first open SQL Data Explorer, a query that counts the number of distinct users who have played your game in the last seven days is shown. You can try this query out or delete it and build your own.
The Glossary panel provides a list of parameters you can use in your query. Use the copy button to copy parameters to the clipboard. The glossary terms are pulled from two sources: the database column names (such as EVENT_DATE
) and custom parameters parsed from the event json (see Snowflake documentation on how to query JSON data). You can define custom parameters depending on the events you send. Some parameters are fields specific to Snowflake, which can change the syntax in the SQL. A list of available tables and their columns can also be found on the SQL Data Explorer queryable tables page.
Database column names are more performant for querying than the parameters parsed from JSON and should be preferred when possible.
If a parameter is represented by a column (such as USER_COUNTRY
), the query uses it as:
`USER_COUNTRY`
If a parameter comes from the event itself, named missionName
in this example, it's accessed via:
`EVENT_JSON:missionName::STRING`
For more information about building custom events, see the create a custom event tutorial.
After running a query, you need to set up the chart. You can toggle between a bar chart, line graph, area graph, pie chart, and stacked bar chart. Currently, two Y axes and one X axis are supported.
To rename an axis label, use the as
expression in your SQL query.
If you run a query without any data ordering, it's possible that your charts won't be an accurate representation of your data as it's not sorted. A warning will be displayed in this instance and it's recommended to order your query through the use of an order by
keyword.
Under your chart is a table of results, showing the columns and result of your query.
Use reports to save your queries. The Reports selector provides a list of all saved queries so you can reload and use them later.
Use the Environments selector to switch between Unity Environments.
For information on all the tables and columns available, see the SQL Data Explorer queryable tables page.