Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(docs): tidy up supported DB engines for metadata store #24080

Merged
merged 1 commit into from
May 16, 2023
Merged

chore(docs): tidy up supported DB engines for metadata store #24080

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions docs/docs/frequently-asked-questions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,17 +186,14 @@ table afterwards to configure the Columns tab, check the appropriate boxes and s
### What database engine can I use as a backend for Superset?

To clarify, the database backend is an OLTP database used by Superset to store its internal
information like your list of users, slices and dashboard definitions.
information like your list of users and dashboard definitions. While Superset supports a
[variety of databases as data *sources*](https://superset.apache.org/docs/databases/installing-database-drivers/),
only a few database engines are supported for use as the OLTP backend / metadata store.

Superset is tested using Mysql, Postgresql and Sqlite for its backend. It’s recommended you install
Superset on one of these database server for production.
Superset is tested using MySQL, PostgreSQL, and SQLite backends. It’s recommended you install
Superset on one of these database servers for production. Installation on other OLTP databases
may work but isn’t tested. Column-store, non-OLTP databases are not designed for this type of workload.

Using a column-store, non-OLTP databases like Vertica, Redshift or Presto as a database backend
simply won’t work as these databases are not designed for this type of workload. Installation on
Oracle, Microsoft SQL Server, or other OLTP databases may work but isn’t tested.

Please note that pretty much any databases that have a SqlAlchemy integration should work perfectly
fine as a datasource for Superset, just not as the OLTP backend.

### How can I configure OAuth authentication and authorization?

Expand Down