SQL Data Explorer is now available

We have some very exciting news to share with you today.

SQL Data Explorer is now available to all UGS beta customers
SQL Data Explorer enables you to query your events data using SQL and extract insights and information that may not be accessible through other Analytics features. Results can be visualized in charts or read from the table of results easily. You can read the documentation here.

What is the impact of this?
The SQL interface will be familiar to data-literate UGS users, and enables them to dive into the event data submitted by their players’ devices to answer questions that they previously couldn’t.

Examples include:

  • A breakdown of custom KPIs on a daily/weekly/monthly basis,
  • Transforming and aggregating event data to produce custom reports.
  • Investigating issues that may be impacting players, retention, or gameplay

How can I report issues or share feedback?
You can share feedback here on the forum, we really value your feedback and can’t wait to hear from you. Let us know if there are any reports or queries that you need help with or want to share with others.

4 Likes

Hi @Laurie-Unity

Think I’ve hit an issue with regards to editing.

These were the steps…

  1. Created working SQL command
  2. Saved report (entered report name)
  3. Edited SQL command (changed field name)
  4. Saved report (it prompts for another name and if you enter the same name it informs you a report with that name already exists)

So it seems once a report is created, it can’t be edited without creating a new report (with an unused name)

For existing reports, save should just overwrite surely?

On-top of that, there doesn’t seem to be an option to delete existing reports.

Hi @Laurie-Unity

It looks like I’ve stumbled across another issue as well.

I’ve a very simple query that returns two columns…

CATEGORY
COUNT

X-Axis is set as CATEGORY/TEXT
Y-Axis is set as COUNT/NUMBER

Now the table shows the expected result…

CategoryA / 4
CategoryB / 2

But the chart (whilst the layout is correct) shows the following…

CategoryA / 2
CategoryB / 4

If you can’t reproduce the issue, pm me and I’ll send the query across.

As a side note, it might be more intuitive to have the chart definition fields as X/Y rather than Y/X. But maybe that’s just personal preference :slight_smile:

@PeachyPixels Great feedback again, we are looking into this. We believe we have already identified the issues that you’ve reported. We will provide a follow up and potential work around shortly.

1 Like

Hi David,

Thanks again for the great feedback. As Jeff mentioned, we are aware of a few issues with the new SQL Explorer tool, the team are working hard to resolve the issues and you will see updates over the coming days and weeks.

Each of the issues you raised has been confimred and there is a workaround on one of them:

  • Can’t update a saved report
  • Can’t delete a saved report
  • Y/X chart setup order would be more intuitive as X/Y
  • Chart Axis and Values get out of sync.
  • This seems to occur if you don’t specify an ORDER in your query, but can to be resolved if you do explicitly specify the order.*
  • e.g.*

csharp* *select EVENT_NAME, count(*) from EVENTS where EVENT_DATE > CURRENT_DATE-2 group by EVENT_NAME order by EVENT_NAME;* *

I hope that helps

Thanks,
Laurie

1 Like

Thanks for the updates both.

I’ve added an explicit order and can confirm it does workaround the issue.

1 Like

Just a quick one to say that I can see the change and it’s far more intuitive now.

Thanks @Laurie-Unity :slight_smile:

1 Like

Hi @Laurie-Unity ,

I see the delete report feature has been added, thanks for that.

It appears to logically delete the reports (which is fine) but it doesn’t allow old report names to be re-used.

Given that reports are currently un-editable, as a workaround I tried this…

  1. Save ReportA as ReportB (so both reports exist)
  2. Delete ReportA (which removes it from the list)
  3. Save ReportB as ReportA (results in a ‘report already exists’ error message)

Hope this helps!

Hi David,

Thanks for bringing this to our attention. I have been able to re-produce the error and have logged a bug ticket.

regards,
Laurie

1 Like