Documentation Data Sources FAQs

Add multiple schemas per data source connection

We’re able to pull multiple schemas for new Redshift, BigQuery, Snowflake, Athena and PostgreSQL sources. For other data sources, you currently can only have one schema per data source connection in Chartio, so you’d need to add any additional schemas as separate data sources.

As a workaround, you can create custom tables that pull from tables in your other schema(s). Custom tables allow you to write SQL that Chartio inserts directly into Interactive Mode queries. So, you can create a custom table with the following SQL (replacing schema_name and table_name with relevant information from your database):

select * from schema_name.table_name

For reference, you can run the following command to view all available tables and views in all schemas (MySQL/PostgreSQL):

select * from information_schema.tables

Reflect multiple schemas

If Chartio supports multiple schemas for your database, you can reflect them into one data source in Chartio. In order to do that, simply leave the Schema Name field in the Connection tab blank.

Note: If you’d like to connect only one of your schemas to Chartio, you can specify the specific schema in the Schema Name field.

Schema field in Direct Connection form

Then navigate to the Schema tab and click the Refresh Schema button. Select which schemas you want to reflect into Chartio, then click Apply.

Now you can view your schemas from one data source within Chartio and easily create charts from tables across schemas.

Multiple-schema source

Delete schemas

Check out our Manage Schemas page for more information about deleting schemas from Chartio.

How to list all available schemas

Most schemas are defaulted to public unless a specific schema is used. To find out which schema to reflect for your data source, you can run the following query on your data source to list all available schemas; however, not all data sources have this functionality.

Amazon Redshift

select * from pg_namespace;


select schemaname from syscat.schemata


You can leave the schema blank since for MySQL, physically a schema is synonymous with a database.




select nspname from pg_catalog.pg_namespace


show SCHEMAS [ from catalog ]


show schemas;

SQL Server

select * from sys.schemas


select table_schema from v_catalog.tables