Skip to main content

User Guide

Troubleshooting SQL Queries

This table attempts to assist you when you experience issues querying data. To learn about any release-specific issues with querying data, see "Known Issues and Limitations" in the DSP Platform Release Notes.

Table 3. Troubleshooting SQL Queries

Issue

Cause

Resolution

No data returned with error

If an asset you are connecting to has multiple fields with the same assigned data class, it's possible that the platform will not know which one to evaluate. It will then generate an error and stop provisioning.

Modify your query to exclude assets with multiple fields with the same assigned data class.

No data returned without error

It is possible that you are attempting to query data through a project to which you do not have authorized access.

Alternatively, if the default policy is drop field, it might be that no policies or rules apply to the data that you are querying.

Talk with a data guardian about what policies and their conditions apply to the data that you are querying.

Error message references unsupported data types

Your query contains unsupported data types.

Include only supported data types in your query.

Error message stating object <table name> not found

Possible causes include:

  • Some drivers don't provide a default schema

  • Table does not exist on the schema that you are querying

  • Incorrect capitalization for databases that are case sensitive

  • Try to fully qualify your table (schema.table) , as some data source drivers do not provide a default schema.

  • Double-check the table name and schema name.

  • Double-check your capitalization.