General Improvements with GainSeeker version 8.6

 

Contents  [Hide]

 

Major new features in GainSeeker version 8.6

Expanded data fields

If you have ever struggled to shorten crucial information to fit GainSeeker's field length limits, then you'll be glad to hear about our new options for expanded data fields!

You can now define a maximum field length of up to 240 characters for the following fields:

For more information, see Setting up Expanded data fields.

MariaDB database support

GainSeeker version 8.6 has been tested on MariaDB - a free, open-source database that can be used in place of the MySQL database. MariaDB is now supported as one of five GainSeeker database options available. For more information, see Database Requirements.

Reduced database size on Microsoft SQL Server, MySQL, and MariaDB

GainSeeker now creates all new tables with variable-length character (varchar) columns, instead of the fixed-length character (char) columns required by previous versions of GainSeeker, on Microsoft SQL Server, MySQL, and MariaDB. The resulting GainSeeker tables can be significantly smaller than their previous counterparts - particularly for the SPC and DMS auxiliary tables such as VDAT_AUX and DDAT_AUX.

If you are upgrading from a GainSeeker version prior to 8.6 and use one of these databases, you can reduce the size of your GainSeeker database by moving your data into these newer tables. This is purely optional, as GainSeeker continues to support the larger tables created by previous versions. For more information, see Reducing database size with varchar columns.

Multiple Modules

GainSeeker Inspections

PC Collect

Python

System Administration

.Launch

Online User Guide

More information