Skip to main content

Database Connections

Connect to a Database

Connections are entry points to your databases, represented by top level nodes in your left area. There are three ways to establish a connection to a local or remote database:

  1. Database Connection popup – which can be called anytime, even after the connection has been established (through any of these methods) and metadata imported, to eventually change some properties.
    1. Click on the “add connection” hyperlink.
    2. Through the File – Open Database Connection menu item.
    3. With the Connect toolbar button, using a specific database type.
    4. Contextual Properties item, while on a database connection node, after the metadata was imported.
  2. Open a database file – for file-based small databases with no security (password) set, such as:
    1. Microsoft Access – from .MDB or .ACCDB files.
    2. SQL CE – from .SDF files.
    3. SQLite – from .DB, .DB3, .SL3, .SQLITE files.
    4. Firebird – from .FDB files.
  3. Batch Connection Loader – from connection strings exposed in clear in a text file. This is not a recommended approach, but if you repeatedly reconnect to many databases and do not have security concerns exposing passwords in a local file on your computer, customize the ConnectionStrings.txt file from your AppData\Local\Xtractor user folder. Line format:
    1. {database_type}; – like {MySQL}, {MariaDB}, {Amazon Aurora} etc, with the same exact name identifier as the menu items under the Connect toolbar button. Prefix with a – (minus sign) a temporarily disabled connection.
    2. valid ADO.NET connection string – this might include the Password, in clear.
    3. one TAB character, followed by an optional short textual description.

Database Connection Properties

database-connection-popup

 

  • A connection Password is never exposed in clear, ever. If saved, it will be masked by ***** in the Connection String property. This supports scenarios such as DBA (DataBase Administrator) establishing a connection string to another end-user, the end-user never knowing what the password was.
  • When User Name and Password credential are provided, and Save Password is True, the encrypted Password is saved in our local database and you automatically later reconnect to the database. If Save Password is False, you’ll be required to provide the Password again when you restart the application.
  • If you connect to a server with more than one database, you have to select one single database, from the Database field, when exposed. The list is usually repopulated after a valid connection to the server was possible, by filling-in the other valid related fields (from the Data Source and Authentication categories).
  • A Test may also show (and save) the database server version, if available, for a successful connection.
  • Other Properties is the field where you may pass any other property=value; extensions. On an established connection, you may see here other properties automatically added by our application and usually required for that type of connection.

Leave a Reply

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close