...

Enable wire logging
In case of connection issues between the Smart Client and the Application Server and all

Enabling of WebStart loggin

Enabling of WebStart console

Enabling of tracing

Smart Client disconnection issues

...

Database Connectivity

General

...

Is the required JDBC driver available?

...

Servoy comes bundled with a limited set of JDBC drivers, due to licensing. For example, we are it is not allowed to ship bundle JDBC drivers of Oracle or the official Microsoft SQL server JDBC driver. See the database section of the Servoy stack info for a list of the shipped JDBC drivers. If no JDBC driver is listed for the database to which a connection needs to be made, it needs to be added manually. See Database Connectivity > JDBC Drivers for more details on which JDBC driver to use and how to add it.

...

Is the database up and running?

...

While obvious that the database needs to be up and running in order for it to be used, it does happen quite often that the source of connectivity issues boils down to the database not being started. Note that the Servoy Application Server doesn't start any database!

...

The Tables & views do not show up in Servoy Developer/errors on the server about missing tables/views while the connection itself seems to work

...

Check that the schema and catalog properties of the database server settings are set correctly. These two properties are send to the database and based on those the database/JDBC driver filters the visible Tables/views for the connection

...

Errors because the connection to the database is lost

...

Oracle

When connecting to Oracle databases, make sure to use the correct version of the Oracle JDBC driver. Each oracle Oracle database version has it's own version of a JDBC driver and when connecting to Oracle with a JDBC driver that was meant for another version of Oracle, the results can be mixed  

...

In order to connect to SQL Server using JDBC, the TCP/IP option of SQL server needs to be enabled, which it isn't by default. If this is the case, a error similar to the following can be found in the log: "com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed."

MySQL

...

Connection to database lost

...

MySQL is notorious for dropping idle connections after a certain timeout. This can be prevented by using the following  "validation query" for the Database Server connection: "select 1", at the cost of a little overhead. It's preferred to configure MySQL to use longer timeouts.