Manage Data Sources
After creating a data source, you can manage it from the Data Sources page. This includes viewing available tables, refreshing the table list, updating connection settings, and organizing multiple database connections for easier management.
Permission Required
Only users with administrative privileges can modify connection settings. Other users can access the data source for querying and reporting, but cannot change its configuration.
View Tables
To browse the tables available in a connected database:
- Open the Data Sources page.
- Select the data source you want to explore.
- The list of available tables will be displayed, allowing you to use them when creating queries, charts, and dashboards.
Refresh the Table List
If new tables have been added to your database after the data source was created, you can refresh the connection to retrieve the latest schema.
- Open the required Data Source.
- Click the ⋯ (More) menu.
- Select Refresh Tables.
Insights will reload the database metadata and update the list of available tables without requiring you to recreate the connection.
Tip
Refresh the table list whenever new tables or views are created in your database to ensure they appear in Insights.
Edit Connection Settings
Database connection details can be updated whenever necessary, such as after changing credentials or migrating a database server.
Administrators Can
- Update database credentials.
- Change the database name.
- Modify SSL or secure connection settings.
- Update other connection-related configuration.
Regular Users Can
- View available tables.
- Create and run queries.
- Build charts and dashboards.
- They cannot modify the connection configuration.
Organize Multiple Data Sources
When working with several databases, use clear and descriptive names so that each connection can be easily identified.
Include details such as:
- The purpose of the database.
- The database technology.
- The environment (Production, Staging, Development, etc.).
Examples:
- Production Sales PostgreSQL
- Staging Site DB
- Marketing Analytics MySQL
- Finance Data Warehouse
Best Practice
Use a consistent naming convention across all data sources. Including the environment and database type in the name helps prevent accidental connections to the wrong database, especially when managing production and staging environments.
