SQL tests let you write bespoke tests that fit your business circumstances and can be run on any table tracked by SYNQ through a unified workflow.

Example—An SQL test runs a query to check for rows where the workspace is null. If any rows match the test, it will throw an error

​
Creating a SQL test

  • Head to the Health overview

  • In the SQL tests section, click Add sql test

  • Select the connection to execute your SQL query

  • Specify a SQL query. The test is considered a success if it returns zero records. If any records are returned, the test will trigger an error, and the failed records will be stored for auditing purposes.

  • Choose a schedule (hourly/daily) and a time (hh: mm) when you want the test to run.

Running an excessive amount of tests or running a test too often will impact your data warehouse costs. Avoid running tests more often than needed

  • The confirmation page will show you a summary of the setup. To make it easier to locate in the SYNQ UI, you can give the test a human-friendly name.

​
Editing a SQL test

  • Head to the Health overview

  • Click on SQL tests to see all your SQL tests

  • Select the SQL test you want to edit by clicking on it

  • In the popout, navigate to the settings tab. Click Edit under SQL test configurations to edit the name, run schedule, or SQL code. To delete the test, click Delete SQL test

SQL tests let you write bespoke tests that fit your business circumstances and can be run on any table tracked by SYNQ through a unified workflow.

Example—An SQL test runs a query to check for rows where the workspace is null. If any rows match the test, it will throw an error

​
Creating a SQL test

  • Head to the Health overview

  • In the SQL tests section, click Add sql test

  • Select the connection to execute your SQL query

  • Specify a SQL query. The test is considered a success if it returns zero records. If any records are returned, the test will trigger an error, and the failed records will be stored for auditing purposes.

  • Choose a schedule (hourly/daily) and a time (hh: mm) when you want the test to run.

Running an excessive amount of tests or running a test too often will impact your data warehouse costs. Avoid running tests more often than needed

  • The confirmation page will show you a summary of the setup. To make it easier to locate in the SYNQ UI, you can give the test a human-friendly name.

​
Editing a SQL test

  • Head to the Health overview

  • Click on SQL tests to see all your SQL tests

  • Select the SQL test you want to edit by clicking on it

  • In the popout, navigate to the settings tab. Click Edit under SQL test configurations to edit the name, run schedule, or SQL code. To delete the test, click Delete SQL test