Connect to the OpenEdge database by using the SQL Explorer
- Last Updated: January 17, 2024
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
SQL Explorer is a Java-based tool used to execute OpenEdge SQL statements in an
interactive format. It is not intended for building applications and should not be
distributed with production software. SQL Explorer is a flexible tool that purposely
accepts the injection of any valid SQL input. You can use this tool in a controlled,
secure environment to view records in a database using SQL commands or test SQL
queries.
Note: SQL Explorer is an add-on SQL JDBC testing
tool designed to be used primarily during development. While SQL Explorer can be a
helpful tool in testing and debugging SQL queries, Progress recommends using it with
caution and only during the development phase. The SQL Explorer tool is not intended
for usage in production environments; therefore, it must not be used
inappropriately.
You can connect to the OpenEdge database from the command line of the proenv session.
To connect to an OpenEdge database from the command line of the
proenv
session, start a proenv prompt and execute
the sqlexp command as
follows:sqlexp -db <databaseName> -H <host> -S <port> -user <username> -password <password>For
example:
sqlexp -db sports2000 -H localhost -S 9999 -user pub -password pubNote: Apart from SQL
explorer, you can also use third-party SQL client utilities, such as
DbVisualiser or the Squirrel SQL client to connect to the OpenEdge
database.
Note: Terminate the SQL queries and statements with a semicolon
(;), if you are using the SQL explorer.
The SQL Explorer tool provide the AutoCommit property that allows you to avoid
the explicit mention of the commit command after each SQL statement. The commit
statement itself gets executed by the server after each SQL statement. You can set
the AutoCommit property in SQL Explorer by means of the following
syntax:
SQLExplorer> @ property_name value ;
SQLExplorer>@autocommit true;The values are written to WRKDIR/SQLExplorer.properties file.
You can also edit the
SQLExplorer.properties
file found in the working directory after you exit the
sqlexp connection. Change the AutoCommit property from the default false to true.#C:\wrk102a\SQLExplorer.properties
#Aug 19, 2021 3:17:09 PM
EchoSql=false
Connect=jdbc:datadirect:openedge://localhost:6000;databaseName=joe
AutoCommit=true
HasFetchLimit=true
ColumnWidthLimit=25
ColumnWidthMinimum=1
...
...
...