You can run queries against the local database just like you would against any SQLite database. My preferred approaches are using DB Browser for SQLite or a Jupyter notebook (mainly because that way it’s easier to visualize results in graphs).
A few of the queries below are used internally by OpenSpartan Workshop to generate in-app visualizations (like the match data). But why limit yourself to the application when you can slice and dice the data in whichever way you want, giving you even deeper insights.
If you are a Python user, you might want to start with the Jupyter Notebook collection that I maintain. It showcases both SQL query examples, as well as visualizations using Seaborn.
To get you started, here are a few sample queries that you can use to explore the content in the database. Substitute my XUID below (when looking for PlayerId) for your own. Your XUID is in the format of xuid(YOUR_PLAYER_NUMERIC_ID) and can be obtained by:
Looking at the name of the database file.
Looking into OpenSpartan Workshop settings - XUID is displayed after you log in.
Looking inside the ServiceRecordSnapshots table
Caution
Running queries yourself while OpenSpartan Workshop is trying to get the data or insert data in the database may result in OpenSpartan Workshop instability and/or data corruption. Don’t do both at the same time.
Danger
All the queries below are non-destructive - that is, they don’t alter any of the data, but because the database is in your possession you can also run destructive queries (e.g., modify data or remove entries). While I can’t stop you from doing that, know that it also may result in OpenSpartan Workshop instability, so do that at your own risk.