Adminer

Connecting to SQLite, MS SQL, Oracle, and MongoDB

DBEverywhere uses Adminer for all database engines other than MySQL and MariaDB. This includes PostgreSQL (covered in its own guide), SQLite, Microsoft SQL Server, Oracle, and MongoDB.

Microsoft SQL Server

  1. Select MS SQL as the database type on the connection form.
  2. Enter your connection details:
  3. Host: your SQL Server hostname or IP
  4. Port: 1433 (default for SQL Server)
  5. Username: your SQL Server login
  6. Password: your password
  7. Database name: the database to connect to
  8. Click Connect.

Make sure DBEverywhere's IP address is allowed through your server's firewall and that TCP/IP connections are enabled in SQL Server Configuration Manager. Remote connections must be enabled in the server properties.

Oracle

  1. Select Oracle as the database type.
  2. Enter your connection details:
  3. Host: your Oracle server hostname
  4. Port: 1521 (default Oracle listener port)
  5. Username: your Oracle user
  6. Password: your password
  7. Database name: the service name or SID
  8. Click Connect.

Oracle connections require the Oracle listener to be accepting remote connections and the firewall to allow DBEverywhere's IP on the listener port.

MongoDB

  1. Select MongoDB as the database type.
  2. Enter your connection details:
  3. Host: your MongoDB server hostname
  4. Port: 27017 (default MongoDB port)
  5. Username: your MongoDB user (if authentication is enabled)
  6. Password: your password
  7. Database name: the database to authenticate against (usually admin for the auth database, then navigate to your target database in Adminer)
  8. Click Connect.

For MongoDB Atlas or other managed MongoDB services, make sure DBEverywhere's IP address is in the IP Access List.

SQLite

SQLite is a file-based database, not a server you connect to over a network. Adminer supports SQLite, but using it through DBEverywhere requires the SQLite file to be accessible on DBEverywhere's server — which it typically isn't, since your SQLite files are on your own machine or server.

In practice that means SQLite isn't something you can manage through DBEverywhere. If you need a browser UI for a SQLite file, run Adminer on the machine that holds the file.

IP Whitelisting

All database engines require DBEverywhere's IP address to be allowed through the database firewall. This applies equally to MS SQL, Oracle, and MongoDB — not just MySQL and PostgreSQL. See How to Whitelist DBEverywhere's IP Address for the current IP and provider-specific instructions.

What You Can Do in Adminer

Once connected, Adminer provides a consistent interface across all engines:

  • Browse and edit data
  • Run queries in the database's native query language
  • View and manage tables, views, and schemas
  • Import and export data
  • Manage users and permissions (where supported by the engine)
← Connecting to PostgreSQL with DBEverywhere "Connection Failed" — How to Fix It →