Skip to content
English
  • There are no suggestions because the search field is empty.

K1 K1RS/RPM Reset

Search

K1 K1RS/RPM Reset

Overview
Each year, K1 Speed resets their RPM (they call it K1 Race Score/K1RS) back to 1200 on January 1 at midnight. This procedure ensures that all locations are finished replicating their data to the other locations and then resets the RPM/K1RS back to 1200.  Step 1: Ensure Replication is Complete at All K1 Locations

If rows are returned that are recent, run replication manually by double clicking C:\ClubSpeed\cs_replication\cs_replication.exe. The launches and runs in the background. It takes about 10-15min to complete. You may look in Processes to see it active. It also logs into C:\ClubSpeed\cs_replication\logs.

If rows are returned that are NOT recent or the replication is otherwise stuck, you can forcefully mark data as having been replicated. Make a note of the IDs that are stuck for later investigation and to ensure that the results of the top 250 are not impacted.

Note the highest ID that you would like to mark as "replicated" and run this query, replacing 123456 with your ID number:

Step 2: Backup/Reset RPM/K1RS (After Step 1 is Done at ALL Locations)


Only perform these steps after the TriggerLogs table at all K1 locations do not return any rows eligible for replication. If this is not the case, replication will overwrite the RPM scores that you reset below.

  1. Backup Customers table:
    SELECT CustID, RPM, Fname, Lname, Address, Address2, City, State, Zip, EmailAddress, PhoneNumber, PhoneNumber2 INTO RPM_Backup_2015 FROM Customers
  2. Reset all RPMs to 1200:
    UPDATE Customers SET RPM = 1200

Step 3: Verify the Reset


To verify that the scores have been reset, visit the top RPM page at each location: http://k1sacramento.clubspeedtiming.com/sp_center/SpeedLimit.aspx

How to Pull Top 250 RPM/K1RS Scores This can be done from one location if replication is in sync. It will calculate from the table backup made in Step 2.1.   Once the query is run, save the results to CSV. It is helpful to spot check several locations to verify that replication was indeed working.

Related Articles