Scriptcase Help Center
en
Language
en English pt_BR Portuguese (Brazil) es Spanish

Filtering Connection Database - Oracle

Open in
View as Markdown Open in ChatGPT Open in Claude
Á

Álvaro Moura

Last updated on Jul 6, 2026

On various occasions, we encounter slowness when connecting to the database or while editing and executing applications. It is possible to resolve these issues by optimizing data loading through filter configuration. To do so, follow these steps:

Step 1 - Creating the Connection

Access the “Database > New Connection” menu to create a new connection in your project.

Step 2 - Selecting the Database

Choose the database — in our case, "Oracle."

Step 3 - Configuring Connection Parameters

Now, the following connection parameters will be needed:

  • Connection Name: You can use any name to identify the connection — by default, Scriptcase sets the name as “conn_oracle.”
  • DBMS Driver: We should select the appropriate connection driver according to the Oracle database.
  • Database Name: We can directly use the IP/TSNAME to connect to the desired database.
  • Schema: SCHEMA of the database to be used.
  • Username: Oracle database user.
  • Password: Oracle database password. Once filled out, click “Test Connection.”

Step 4 - Configuring the Connection Filter

At this point, we should take the following steps to optimize our Oracle database connection configuration:

Show: We choose which database items will be displayed when creating applications.

  • Tables
  • Views
  • System Tables
  • Procedures

Filters: Here, we can configure two items with the following options:

  • Tables: We can type the names of the tables to be used in the configuration.
  • ​****Owner: We should use the name — always in uppercase — of the SCHEMA, to show or not in the table list when creating the application.
  • Show: Defines whether the data entered in "Tables" and/or "Owner" will be displayed or not.

Once configured, click "Save".

Info

In the example below, only the "SYSTEM" SCHEMA data will be displayed when creating applications.

Conclusion

By following these steps, we avoid loading all SCHEMAS or tables from the database, reducing the amount of data requested from the database and increasing the speed of application creation, editing, and execution.