Database Settings

A database connection needs additional to the IP parameters more information. These details are different from one database to the other.

Mostly all databases need a user and password for accessing it. All other parameters are different between the databases. Some databases will need special settings in the database itselve like detail settings or licenses.

MySql

The MySql database knows schema. A standard schema can be defined in the database. If doing so the schema field can be left empty.

More details are encryption, packaging and more. Detailed information to these parameters are described in the original database manuals.

Microsoft SQL

The MS-SQL database uses instances. So an instance must be given always. If the required parameters can not checked online please ask your database system operator for the details. Do not forget entering the port number which is different between instances.

The Sybase database uses the same protocol as Ms-SQL. Normally all will work, but it is more secure checking "Enable Sybase compatibility" if Sybase is used.

A hint: Browsing works in Microsoft databases only if the user has administrator rightss.

There are two methods to connect to a server:

1. IP-Address or Domain Name an Port

2. Microsoft Domain and Share name. Enter this as "domain\share".

Postgres SQL

A user, password and database need to be configured. Postgres uses the database as a security feature, so it can not be browsed.

ODBC

Under Windows please configure the ODBC data source as system DSN. PLC Engine Collect works as a service, so user DSN can not be accessed..

Configure the ODBC driver completely..

Browsing

Use the browse functionality if ever possible. This will need online access to the database. In the database core the users will need the rights for browsing.

In case of questions ask your database administrator.

Most databases are giving detailed error information. They will be written into the diagnostics logger.

Cache

If data are written only into the database the data can use a file cache if the database connection is broken.

The data are stored into the given file.

Often files lying on flash devices. Such flash memory can not be written very often. So PLC Engine Collect has an additional memory cache before it writes the data into the file. The memory cache has 1MB in size. If the memory runs over before the time limit is reached the data will be written into the real file earlier.

If the database connection will work again the file data will be sent to the database. If all data are send and verified by the database the file will be deleted.

See also: Enable file caching in Database request