Need help with SeeQR?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

open-source-labs
223 Stars 44 Forks MIT License 1.1K Commits 0 Opened issues

Description

A database analytic tool that allows a developer to compare the efficiency of different schemas and queries on a granular level to make better informed architectural decisions regarding SQL databases at various scales.

Services available

!
?

Need anything else?

Contributors list

No Data

PRs Welcome Release: 4.0 License: MIT Contributions Welcome Twitter Github stars Tests

theSeeQR.io

SeeQR: A database analytic tool to compare the efficiency of different schemas and queries on a granular level so that developers/architects can make better informed architectural decisions regarding SQL databases at various scales.

Table of Contents

Getting Started

To get started on contributing to this project:

  1. Download and install Postgres.app and start it before opening up SeeQR
  2. Ensure that psql is available in the
    $PATH
  3. Ensure that a 'postgres' role exists
  4. Download the latest version of SeeQR

Built With

Interface & Features

  • Overview

    • Upon application launch, select the desired database to connect to or follow the quick-start guide to get started
    • The application connects to the local instance of PostgreSQL using the role 'postgres', so all databases that 'postgres' has access to are available
    • Besides using the existing databases, the application also provides various options to create new databases:
      • Importing
        .sql
        or
        .tar
        files
      • Manually running
        CREATE DATABASE
        queries in SeeQR
      • Copying an existing database (with or without original data)
    • Users can toggle between the 'DATABASES' view and the 'QUERIES' view
  • Databases

    • In the 'DATABASES' view, users can select a table from a list of all the tables in the schema of the currently selected database
    • Information about the selected table is then displayed
    • The name and size of the selected database are also displayed at the top of the page
    • Users can also generate large amounts of foreign-key compliant dummy data for the selected table in the current database. Currently supported data types are:
    • INT
    • SMALLINT
    • BIGINT
    • VARCHAR
    • BOOLEAN
    • DATE


  • Queries

    • In the 'QUERIES' view, the main panel is where the query input text field is located, utilizing CodeMirror. The paint button in the top right corner of the panel auto-formats the inputted query
    • Users can select the database to use in the 'Database' dropdown above the main panel
    • Users also have the option to execute a labelled or unlabelled query — simply provide a label in the 'Label' field above the main panel to identify the query in later comparisons against other queries
    • Please note that only labelled queries will be saved in the current session for future references
    • To execute the query, simply select the 'RUN QUERY' button at the bottom of the panel or press 'Ctrl-Enter' on the keyboard


  • Data

    • Once executed, the query's output will be displayed. In addition, for eligible queries, users will be able to view the queries' planning time, execution time, total run time, and plan of execution
    • Eligible queries include any
      SELECT
      ,
      INSERT
      ,
      UPDATE
      ,
      DELETE
      ,
      VALUES
      ,
      EXECUTE
      ,
      DECLARE
      ,
      CREATE TABLE AS
      , or
      CREATE MATERIALIZED VIEW AS
      statement
    • Users can toggle between the executed query's 'RESULTS' and 'EXECUTION PLAN'
    • The 'RESULTS' view displays the executed query's returned results
    • The 'EXECUTION PLAN' view displays the executed query's plan of execution
    • Within the 'EXECUTION PLAN', users can adjust the thresholds of 'Percentage of Total Duration' and the 'Planner Rows Accuracy' that are used to highlight certain nodes in the tree
      • The 'Percentage of Total Duration' threshold is used to highlight the nodes whose durations are higher than the set limit, indicating that these nodes may be areas of improvement
      • The 'Planner Rows Accuracy' threshold is used to highlight the nodes for which the planner's estimate number of rows differs from the actual number of rows, indicating that the database might need vacuuming
    • Clicking on a node will display additional details regarding that action as well
    • To execute a new query, simply select the '+' button in the sidebar. To go back to a previously saved query, just select it in the sidebar


  • Compare

    • Click on the 'bar graph' icon at the top of the sidebar to get to the 'Compare Queries' view
    • The comparison table is flexible to the user’s preferences as the user selects which queries to compare side by side
    • Simply check or uncheck the box next to each saved query to add or remove the query from the graph
    • Graph will be organized along the x-axis by label, and colored by schema
    • Aside from the visualized performance comparison of the selected queries, a table will display information about each selected query, including its total run time and performance relative to other queries with the same label, with the most performant query highlighted

Application Architecture and Logic

Cross-Database Comparisons
One of the key features of SeeQR is to compare the efficiency of executing user-inputted queries against different databases. This allows customization of table scale, relationship, type, and the queries themselves within the context of each database. This flexibility affords the user granular adjustments for testing every desired scenario. Please refer to “Interface & Features” for more details on execution.

Session-based Result Caching
The outcome results from each query, both retrieved data and analytics, are stored in the application’s state, which can be viewed and compared in table and visualizer formats. Note that these results’ persistence is session-based and will be cleared upon quitting the application.

Contributing

We've released SeeQR because it's a useful tool to help optimize SQL databases. Additional features, extensions, and improvements will continue to be introduced. We are thankful for any contributions from the community and we encourage you to try SeeQR out and make or suggest improvements where you see fit! If you encounter any issues with the application, please report them in the issues tab or submit a PR. Thank you for your interest!

Core Team

Casey Escovedo | Casey Walker | Catherine Chiu | Chris Akinrinade | Cindy Chau | Claudio Santos | Faraz Akhtar | Frank Norton | James Kolotouros | Jennifer Courtner | Justin Dury-Agri | Katie Klochan | Mercer Stronck | Muhammad Trad | Richard Lam | Sam Frakes | Serena Kuo

License

SeeQR is MIT licensed.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.