This connection type is used when you wish to connect using a hostname or IP, port number and database service name.

User, Workspace, or Folder scope: Click User, Workspace, or select a workspace folder name from the dropdown to choose the scope of this connection. Connections with User scope are stored in the settings for the user and are available at all times. Connections with Workspace or Workspace Folder scope are stored in a settings file in the workspace, and the connections are only shown in Oracle Explorer when the workspace is open. The connection scope can only be set when the connection is first created and cannot be changed without deleting and recreating the connection.

Database host name: Enter the machine hostname or IP address

Port number: The port number (usually 1521)

Service Name: The database service name (This is usually the same name as the pluggable database name)

Connection String: This connection string can be copied and used to connect elsewhere, such as in a SQL script.

Role: Default (for ordinary use) or SYSDBA or SYSOPERATOR for administrative tasks

Username: Username. For non-proxy connections: Enter database username or use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate). For proxy connections: Enter database username. ("/" (forward slash) is not allowed with proxy connections)

Password: The password. For non-proxy connections: Enter the database password. Leave blank if Username field is "/" (forward slash) . For proxy connections: Enter the database password. Leave blank for single-session proxy. Password is required for two-session proxy.

Save Password: Check this box if you do not wish to enter the password each time. (Passwords cannot be saved for Workspace or Folder scopes)

Set as Default Connection: Makes this connection the default connection, used each time a SQL or PL/SQL script is opened by this extension. This is useful when opening a folder with many SQL scripts. The default connection is identified by an asterix in the upper left hand corner of the database icon in Oracle Explorer.

Connection Name: This is the identifier that will be used in Oracle Explorer.

Color button: Click this button to open a color picker dialog. In the picker dialog, select a color that will be used with the connection name in Oracle Explorer and also in the corresponding code window. This helps visually identify what connection the code window is using.

Show more options: Checking this checkbox displays additional less frequently used options in the dialog.

Proxy Username: The proxy username. (Other tools use the format proxyusername[username]/ [proxypassword]). Use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate)

Proxy Password: The proxy password. (Other tools use the format proxyusername[username]/ [proxypassword]). Leave blank if Proxy Username field is "/" (forward slash) .

Current Schema: The schema shown in Oracle Explorer. Other Schemas may be browsed using the Other Users node.

Append current schema to connection name: Check this box to append the current schema name to the connection name in Oracle Explorer

Login Script: A SQL script that will be run each time this connection is opened. This is useful to alter session settings to modify NLS parameters, etc. This overrides the login script set in the extension settings.

Append "workspace" to connection name: (Workspace scope only) Check this box to append the word "workspace" to the connection name in Oracle Explorer

Append folder name to connection name: (Folder scope only) Check this box to append the folder name to the connection name in Oracle Explorer

Use this connection type if you wish to connect using an alias in a TNSNAMES.ORA file.

User, Workspace, or Folder scope: Click User, Workspace, or select a workspace folder name from the dropdown to choose the scope of this connection. Connections with User scope are stored in the settings for the user and are available at all times. Connections with Workspace or Workspace Folder scope are stored in a settings file in the workspace, and the connections are only shown in Oracle Explorer when the workspace is open. The connection scope can only be set when the connection is first created and cannot be changed without deleting and recreating the connection.

TNS Admin Location: Select the path to the directory containing your TNSNAMES.ORA file (Visit the extension settings to set a default location)

TNS Alias: Select the alias you wish to connect to

Use Wallet File: Check this if using a wallet file

Use Username and Password from Wallet File (SEPS): (This checkbox becomes visible once Use Wallet File is checked). Check this box if using the username and password stored in the wallet file located in the Wallet File Location directory using Secure External Password Store (SEPS). This checkbox causes SQLNET.WALLET_OVERRIDE to be set to TRUE for this connection. For non-proxy connections, set the Username field to forward slash "/". For proxy connections, enter the database username in the Username field and set the Proxy Username field to "/" (forward slash).

Wallet File Location: Select the path to the directory containing your wallet file (Visit the extension settings to set a default location)

Role: Default (for ordinary use) or SYSDBA or SYSOPERATOR for administrative tasks

Username: Username. For non-proxy connections: Enter database username or use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate) or if using SEPS wallet for database username and password. For proxy connections: Enter database username. ("/" (forward slash) is not allowed with proxy connections).

Password: The password. For non-proxy connections: Enter the database password. Leave blank if Username field is "/" (forward slash) . For proxy connections: Enter the database password. Leave blank for single-session proxy. Password is required for two-session proxy.

Save Password: Check this box if you do not wish to enter the password each time

Set as Default Connection: Makes this connection the default connection, used each time a SQL or PL/SQL script is opened by this extension. This is useful when opening a folder with many SQL scripts. The default connection is identified by an asterix in the upper left hand corner of the database icon in Oracle Explorer.

Connection Name: This is the identifier that will be used in Oracle Explorer.

Color button: Click this button to open a color picker dialog. In the picker dialog, select a color that will be used with the connection name in Oracle Explorer and also in the corresponding code window. This helps visually identify what connection the code window is using.

Show more options: Checking this checkbox displays additional less frequently used options in the dialog.

Proxy Username: The proxy username. (Other tools use the format proxyusername[username]/ [proxypassword]). Use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate) or if using SEPS wallet for database username and password.

Proxy Password: The proxy password. (Other tools use the format proxyusername[username]/ [proxypassword]). Leave blank if Proxy Username field is "/" (forward slash) .

Current Schema: The schema shown in Oracle Explorer. Other Schemas may be browsed using the Other Users node.

Append current schema to connection name: Check this box to append the current schema name to the connection name in Oracle Explorer

Login Script: A SQL script that will be run each time this connection is opened. This is useful to alter session settings to modify NLS parameters, etc. This overrides the login script set in the extension settings.

Append "workspace" to connection name: (Workspace scope only) Check this box to append the word "workspace" to the connection name in Oracle Explorer

Append folder name to connection name: (Folder scope only) Check this box to append the folder name to the connection name in Oracle Explorer

Use this connection type if you wish to connect using an Easy Connect Plus connect string or a TNS descriptor (for example, a connection string used to connect to Oracle Cloud).

User, Workspace, or Folder scope: Click User, Workspace, or select a workspace folder name from the dropdown to choose the scope of this connection. Connections with User scope are stored in the settings for the user and are available at all times. Connections with Workspace or Workspace Folder scope are stored in a settings file in the workspace, and the connections are only shown in Oracle Explorer when the workspace is open. The connection scope can only be set when the connection is first created and cannot be changed without deleting and recreating the connection.

Connection string: Enter an Easy Connect Plus connect string or a TNS descriptor

Role: Default (for ordinary use) or SYSDBA or SYSOPERATOR for administrative tasks

Username: Username. For non-proxy connections: Enter database username or use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate). For proxy connections: Enter database username. ("/" (forward slash) is not allowed with proxy connections).

Password: The password. For non-proxy connections: Enter the database password. Leave blank if Username field is "/" (forward slash) . For proxy connections: Enter the database password. Leave blank for single-session proxy. Password is required for two-session proxy.

Save Password: Check this box if you do not wish to enter the password each time

Set as Default Connection: Makes this connection the default connection, used each time a SQL or PL/SQL script is opened by this extension. This is useful when opening a folder with many SQL scripts. The default connection is identified by an asterix in the upper left hand corner of the database icon in Oracle Explorer.

Connection Name: This is the identifier that will be used in Oracle Explorer.

Color button: Click this button to open a color picker dialog. In the picker dialog, select a color that will be used with the connection name in Oracle Explorer and also in the corresponding code window. This helps visually identify what connection the code window is using.

Show more options: Checking this checkbox displays additional less frequently used options in the dialog.

Proxy Username: The proxy username. (Other tools use the format proxyusername[username]/ [proxypassword]). Use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate)

Proxy Password: The proxy password. (Other tools use the format proxyusername[username]/ [proxypassword]). Leave blank if Proxy Username field is "/" (forward slash) .

Current Schema: The schema shown in Oracle Explorer. Other Schemas may be browsed using the Other Users node.

Append current schema to connection name: Check this box to append the current schema name to the connection name in Oracle Explorer

Login Script: A SQL script that will be run each time this connection is opened. This is useful to alter session settings to modify NLS parameters, etc. This overrides the login script set in the extension settings.

Append "workspace" to connection name: (Workspace scope only) Check this box to append the word "workspace" to the connection name in Oracle Explorer

Append folder name to connection name: (Folder scope only) Check this box to append the folder name to the connection name in Oracle Explorer

Use this connection type when you wish to connect using an Oracle Data Provider for .NET Core (ODP.NET) Connection String. This might be useful if you are already using ODP.NET connection strings in a .NET application.

User, Workspace, or Folder scope: Click User, Workspace, or select a workspace folder name from the dropdown to choose the scope of this connection. Connections with User scope are stored in the settings for the user and are available at all times. Connections with Workspace or Workspace Folder scope are stored in a settings file in the workspace, and the connections are only shown in Oracle Explorer when the workspace is open. The connection scope can only be set when the connection is first created and cannot be changed without deleting and recreating the connection.

Connection string: Enter a ODP.NET Connection String

Set as Default Connection: Makes this connection the default connection, used each time a SQL or PL/SQL script is opened by this extension. This is useful when opening a folder with many SQL scripts. The default connection is identified by an asterix in the upper left hand corner of the database icon in Oracle Explorer.

Connection Name: This is the identifier that will be used in Oracle Explorer.

Show more options: Checking this checkbox displays additional less frequently used options in the dialog.

Current Schema: The schema shown in Oracle Explorer. Other Schemas may be browsed using the Other Users node.

Append current schema to connection name: Check this box to append the current schema name to the connection name in Oracle Explorer

Login Script: A SQL script that will be run each time this connection is opened. This is useful to alter session settings to modify NLS parameters, etc. This overrides the login script set in the extension settings.

Append "workspace" to connection name: (Workspace scope only) Check this box to append the word "workspace" to the connection name in Oracle Explorer

Append folder name to connection name: (Folder scope only) Check this box to append the folder name to the connection name in Oracle Explorer

Use this connection type if you wish to connect using a Directory Server (LDAP).

User, Workspace, or Folder scope: Click User, Workspace, or select a workspace folder name from the dropdown to choose the scope of this connection. Connections with User scope are stored in the settings for the user and are available at all times. Connections with Workspace or Workspace Folder scope are stored in a settings file in the workspace, and the connections are only shown in Oracle Explorer when the workspace is open. The connection scope can only be set when the connection is first created and cannot be changed without deleting and recreating the connection.

TNS Admin Location: Select the path to the directory containing your TNSNAMES.ORA file (Visit the extension settings to set a default location)

TNS Alias: Type in the database service name

Use Wallet File: Check this if using a wallet file

Use Username and Password from Wallet File (SEPS): (This checkbox becomes visible once Use Wallet File is checked). Check this box if using the username and password stored in the wallet file located in the Wallet File Location directory using Secure External Password Store (SEPS). This checkbox causes SQLNET.WALLET_OVERRIDE to be set to TRUE for this connection. For non-proxy connections, set the Username field to forward slash "/". For proxy connections, enter the database username in the Username field and set the Proxy Username field to "/" (forward slash).

Wallet File Location: Select the path to the directory containing your wallet file (Visit the extension settings to set a default location)

Role: Default (for ordinary use) or SYSDBA or SYSOPERATOR for administrative tasks

Username: Username. For non-proxy connections: Enter database username or use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate) or if using SEPS wallet for database username and password. For proxy connections: Enter database username. ("/" (forward slash) is not allowed with proxy connections).

Password: The password. For non-proxy connections: Enter the database password. Leave blank if Username field is "/" (forward slash) . For proxy connections: Enter the database password. Leave blank for single-session proxy. Password is required for two-session proxy.

Save Password: Check this box if you do not wish to enter the password each time. (This is not allowed for workspace or folder scoped connections)

Set as Default Connection: Makes this connection the default connection, used each time a SQL or PL/SQL script is opened by this extension. This is useful when opening a folder with many SQL scripts. The default connection is identified by an asterix in the upper left hand corner of the database icon in Oracle Explorer.

Connection Name: This is the identifier that will be used in Oracle Explorer.

Color button: Click this button to open a color picker dialog. In the picker dialog, select a color that will be used with the connection name in Oracle Explorer and also in the corresponding code window. This helps visually identify what connection the code window is using.

Show more options: Checking this checkbox displays additional less frequently used options in the dialog.

Proxy Username: The proxy username. (Other tools use the format proxyusername[username]/ [proxypassword]). Use "/" (forward slash) if using external authentication (i.e. OS/Kerberos/Certificate) or if using SEPS wallet for database username and password.

Proxy Password: The proxy password. (Other tools use the format proxyusername[username]/ [proxypassword]). Leave blank if Proxy Username field is "/" (forward slash) .

Current Schema: The schema shown in Oracle Explorer. Other Schemas may be browsed using the Other Users node.

Append current schema to connection name: Check this box to append the current schema name to the connection name in Oracle Explorer

Login Script: A SQL script that will be run each time this connection is opened. This is useful to alter session settings to modify NLS parameters, etc. This overrides the login script set in the extension settings.

Append "workspace" to connection name: (Workspace scope only) Check this box to append the word "workspace" to the connection name in Oracle Explorer

Append folder name to connection name: (Folder scope only) Check this box to append the folder name to the connection name in Oracle Explorer