Warning: This is a potentially very scary thing to do. You overwrite your live database, and replace it with data from your training database, or vice versa. Do not proceed without a backup of your live SQL data.

 

Please contact Siriusware Technical Support if you do not understand the function of these buttons, or are unsure if you need to use it. It could cause catastrophe if used accidentally!

 

If you run your “live” SysManager, the Copy Data FROM Training System option is available from the menu, and if you run your “training mode” SysManager, the Copy Data FROM Live System is available. Please be careful using these options. This function copies all the setup information from the other system (training or live, depending on which one you are running). It does not copy transactional information − like the transact, sale_hdr, etc., or guest/access information like guests, access, gst_actv, acc_actv, gst_pass, etc. Only the information related to item setup and system preferences is copied. This means that reports run on a data set copied from another using this method does not match − because of the missing transactional information. Here are the tables that can be copied:

(For advanced users, SiriusSQL tables are fully described in the SiriusSQL Data Dictionary, available from Siriusware Client Services.) The following list shows what related tables get copied when you check off a particular group of data to copy. To find out what data is related in the various tables, the copy program inspects the enforced relational table constraints defined in the SiriusSQL database. Some tables may seem completely unrelated to the group you selected, but if there is an enforced relational constraint connecting them anywhere along the chain of related tables, that data must be copied to preserve integrity. There can be some overlapping of table information, so if you check off multiple groups (or all groups) and the table appears more than once, it is copied only the one time. These table lists are not necessarily in alphabetical order. They are in the order the data is copied in order to preserve the relational integrity of the data (i.e., parent department records must be copied before child category records, and so on).