Master/Slave Database

Introduction

The Master/Slave setup allows you to share data between machines. The Master machine (with the Master database) and as many slave machines as required (each with a slave database). The Master/Slave set up can be used to:

• Set up a tournament on a Master machine.
• Move the required sections of a tournament to a slave machine, so that controller can run the sections on their machine.
• Record pairings and results on the controllers machine.
• Pass the sections of the tournament back to the Master database once the tournament has been completed.
• Produce Allow reports and grading information for all the sections of the tournament from the master database.

How To

To export data from a Master database you must have purchased the ‘Coordinator’ package of Tournament Director for Windows.

To set up and run tournaments on a slave database you do not need a registered version of Tournament Director for Windows.

The process to organise a tournament using a master and slave database is as follows:

• Create all the sections for the tournament on the master database, including adding players and any pre arranged byes.
• Create an export folder (Tools->Export Tournaments ) for each controller containing just their sections.
• Pass the data to the controllers of the sections.
• Get each controller to create a new slave database on their machines.
• Import (Tools->Import Tournaments) the controllers data onto the controllers machine ready for the start of the tournament.
• The controller can then run the section on their machine. They can:
  • Add late entries to the sections, record pre-arranged byes, if required.
  • Set up avoid pairings, if required.
  • Print the player cards and wall charts
  • Set up the pairings and record the results for each round.
  • As the tournament progresses, print pairing sheets, result slips and cross tables as required.
  • At the end of the tournament a final cross table, or result list can be produced.
• Once the tournament has been completed the sections can be exported (Tools->Export Tournament ) from the slave database.
• The data can then be loaded back to the master machine.
• Once the sections have been loaded back on the master machine, the results can be submitted to the ECF for grading and the results can be published to the internet results service, if required.

Limitations

A Master and Slave database are related. When database is exported from a Master database, details of the Master database are stored in the export files. When these details are loaded to a new Slave database the systems records a link between the Master and Slave database. Data on the Slave database can only be related to a single Master database.  Data from a Slave database can only be moved back to its original Master database.

It is not possible to move data from one Master database to another Master database.

Master Database

By default, the system creates Master databases.

The ‘Coordinator’ package enables two extra Tools menu options.

• Export Tournaments. Allows data to be exported the current database. This displays the Export Tournament dialogue so that the required tournaments can be selected.
• Import Tournaments. Allows data to be imported to the current database.

Data can only be imported from a slave database on to a Master database if it was originally exported from this Master database.

Slave database

Data can be imported from one and only Master database. However, it is possible to create multiple Slave databases on a machine, so that data from many different Master databases can be administered on one machine.

There are a few limitations on what can be performed on a slave database. For instance:

• New tournaments can not be created.
• Results of a tournament can not be submitted for grading.
• Results of a tournament can not be published to the internet results service.