Go to Scriptcase store

# Connection with Amazon RDS PDO DBLIB

If you do not have the PDO DBLIB driver enabled, check below our documentation on how to enable this driver in Scriptcase for connection.

- To enable the PDO DBLIB: Click here

> ATTENTION: If you do not have an Amazon RDS MSSQL Server base created, check how to create it by clicking here.

## Creating a connection to Scriptcase

See below how to create a connection in your Scriptcase project, using the Enabled Driver (PDO DBLIB) and the Amazon RDS MSSQL Server database.

1 - Access a project from your Scriptcase.

2 - Click the New Connection icon to create a connection

or access the Database> New connection menu.

After that, a screen will appear with all database connections.

3 - Select the Amazon RDS connection.

4 - And choose the Amazon RDS MSSQL Server database.

## Connection

Enter the parameters for connecting to your Amazon RDS PostgreSQL database as follows:

- Connection name: Define the name of your new connection. By default, Scriptcase adds the prefix conn along with the database name.

- DBMS Driver: Select the PostgreSQL Driver for connection. In this example, we use the PDO DBLIB Driver.

- Server/Host (Name or IP): Enter the domain of the Amazon RDS server where the database is installed.

- EX: `database-mssql.us-east-2.rds.amazonaws.com`

- Port: Enter the port for connection. By default, the defined port is 1433.

- Database Name: List and select the database you will connect to.

- EX: `samples`

- Username: Inform the user to authenticate the connection to your database.

- Password: Enter the password to complete the authentication process.

- Test connection: Click this button to get a response to the Scriptcase request to find out if the parameters entered are correct.

## Filter

Accessing this tab, you can configure which Database items will be displayed on the connection, depending on the owner or not.

#### Show

It allows the connection to see tables, views, system tables and procedures depending on the items selected by the user. By default, the items Tables and Views are already selected by Scriptcase.

- Tables: Selecting this option, the tables in your database will be displayed.
  - By default, Scriptcase enables this option .
- Views: By selecting this option, the views of your database will be displayed.
  - By default, Scriptcase enables this option .

- System Tables: Selecting this option, the system tables of your database will be displayed.

- Procedures: By selecting this option, the procedures of your database will be displayed.

#### Searches

Allows you to define which tables and owners are displayed.

- Tables: You can define in this option which tables will be displayed. The configuration can contain a `PREFIX%%` or name of the tables to display.
  - By default, Scriptcase leaves this option empty.
  - EX:

- Owner: Inform the user who sees the tables informed for display.
  - User must be capitalized as in the example above .
- View: Choose whether to display the tables for the informed owner.

> NOTE: By using table filtering, you eliminate unnecessary tables for your project and improves the performance of your database connection.

## Advanced

In this tab, you have access to specific settings for the connection. The settings made in this session impact the data display and application performance.

- client_encoding: Select the encoding used in your database. In the example above, we use the client_encoding utf8.
  - The utf8 charset is set by default.
- Decimal Separator: Select the type of separator for decimal records, between comma and period.
  - By default, the `.` dot is selected as a separator.
- Persistent Connection: Define whether connections will be terminated after the execution of your scripts in Scriptcase applications.
  - By default, Scriptcase disables this option.
- Use the schema before the table name: Define whether the database schema will be displayed before the table names.
  - By default, Scriptcase enables this option.

## SSH

Here are the SSH options available in the image and their descriptions regarding database connection:

#### Use SSH

Enables or disables the SSH tunnel for database connection. When enabled, the database connection will be routed through the SSH server.

#### SSH Server

The IP address or hostname of the SSH server that will be used for tunneling. This is the machine that will act as a bridge to access the database securely.

#### SSH Port

The port used to connect to the SSH server.

#### SSH User

The username used to authenticate with the SSH server. This user must have permissions to establish an SSH connection.

#### Authentication method

You can choose two options: password or certificate. When you choose one of the options, a new field will appear below for the configuration.

#### Private cert. file

The private key file used for authentication if the SSH server requires key-based authentication instead of a password.

#### Local port for port forwarding

The local port on the client machine that will be used for forwarding database traffic through the SSH tunnel. This port acts as a bridge between the database client and the remote database.

#### Database server from SSH

The hostname or IP address of the database server as seen from the SSH server. This is necessary when the database is only accessible within the SSH server’s network.

#### Database port from SSH

The port of the database server that will be accessed through the SSH tunnel. This should match the database service’s listening port.