Database Information

Databases are basically containers for data. Because a public library stores books, we could also say that a library is a database of books. But strictly defined, databases are computer structures that save, organize, protect, and deliver data. A system that contains databases is called a database management system, or DBM.

Relational databases being that of WrightZone Weighbridge are the most common database systems. They include databases like SQL Server, Oracle Database, Sybase, Informix, and MySQL. The relational database management systems (RDMS) feature high level performance for managing data over desktop database programs. For example, they allow multiple users (even thousands) to work with the data at the same time, creating advanced security for access to the data. RDMS systems store data in columns and rows, which in turn make up tables. A RDMS table in the most simplistic of forms is like a spreadsheet.

WZWB Users are typically not concerned with the database neither should they be. All they require is that the WZWB application (connected to the WZWB database) works and of course performs well on tasks the user is requesting of it; being that of a connection to the Scale, completing entry and exit transactions and running reports. To this effect information on the WZWB Database and related content has been kept simple.

Stand Alone

The Stand Alone version of your WrightZone Weighbridge Software means a single Multi-master database only with a block of 5 concurrent user, configuration. With such a configuration there is only the single Primary Connection database tab.

When this is no connection to your WZWB database; notification is provided.

The application will default users to the Primary Connection tab which can be used to test a successful connection this is also reported within your WZWB Footer reporting connected when True.
Should the connection to your database be lost assuming the issue is not hardware related there are just two scenario's with which to consider:

You are using a WZWB Client to connect to the database stored on a server within a local network where connection therefore communication to the server is down and/or;
You are running the WZWB Client on the same server or machine with which the WZWB database is installed and in this situation there is no possibility of a network fault; requiring a start or restart of the WZWB Services (below accessed via right click on your Task Bar, Start Task Manager moving to the Services tab).

Enterprise

The Enterprise version of WrightZone Weighbridge means more than one Multi-master database. It's this configuration that delivers redundancy and continual operations uptime as standard because WZWB Clients are automatically rerouted to a Secondary Multi-master database should a Primary server/databases cease to function. WZWB employs Multi-master replication being a method of database replication which allows data to be stored by a group of computers, and updated by any member of the group. All members are responsive to client data queries. The Multi-master replication system is responsible for propagating the data modifications made by each member to the rest of the group and, resolving any conflicts that might arise between concurrent changes made by different members.

Above shows the most common report upon enquiry of the Database Information window where everything remains online and in sync. More information can be found in the WZWB Technical manual but from an Administrators perspective the following of multiple columns reported are primary in identifying a WZWB application concern should they exist hence is set as the Grid Default view.

Connection name	Name of the master connection.
Slave_SQL_State	State of SQL thread.
Slave_IO_State	Thread has connected to the master and is waiting for binary log events to arrive.
Master_host	Master host that the slave is connected to.
Master_port	The port being used to connect to the master.
Master_Log_File	Name of the master binary log file that the I/O thread is currently reading from.
Read_Master_Log_Pos	Position up to which the I/O thread has read in the current master binary log file.
Relay_Log_File	Name of the relay log file that the SQL thread is currently processing.
Relay_Master_Log_File	Name of the master binary log file that contains the most recent event executed by the SQL thread.
Slave_IO_Running	Whether the slave I/O thread is running and connected (Yes), running but not connected to a master (Connecting) or not running (No).
Slave_SQL_Running	Whether or not the SQL thread is running.
Last Error	Alias for the Last_SQL_Error

Below offers example where users might experience application performance issues and therefore reasoning as to why a WZWB Client has rerouted to a Secondary Multi-master database. On opening the Database Information window and seeing anything less than above and something similar to below contact your Committed Consulting Team.

F11 is a users quick key that will take a screenshot of above or any issue in question attaching the image to an email prepopulated with our address of [email protected] requiring user to send only.