KbA0033: Renaming CopperCube Site will result in a new SQL table

Description

This KbA describes the consequences of renaming a site in the CopperCube GUI in CopperCube v 1.20 and higher. This should not discourage you from renaming your site, especially in cases where a shorter site name is necessary.

Changing the site name will create new SQL database tables. Old data will still be stored under the old site name and will not be converted. Please be wary of this issue when editing your database.

The old data is not merged into the new table, but the new table collects all new data. This means that the data is separated between two tables, and queries on the new site name will not show old data. Any SQL queries will need to merge these 2 data sources to get correct results.

This will not affect Kaizen or enteliWEB and the access of data by these programs.

The SQL navigation tree shows sites with different names being stored as separate folders

Example

  • Old site name: 123ladan-site_qa test long site name2
  • New site name: ladan123

Data collection sequence numbers will end with the old site, and the new site will continue with the newer sequence numbers.

  • 123ladan-site_qa test long site name2 for a given device and TL will have sequence number: 1498,1499,1500,1501.
The start and end seq [PK] integers
  • ladan123 for a given device and TL will have sequence numbers: 1502,1503,1504, etc.
Seq Integer continues where the old integer ended