If you delete the Hits_Track table manually, then CREATE it manually from the SQL monitor, without running the setup.cgi program, the risk is trivial to non-existant.
You are only operating on that specific table, without any automated processes.
The create table command will rebuild the indexes, etc. Then, do the 'defs' back up as indicated before resyncing, so you preserve the 'weights' in the Links and Category tables.
You can manually verify the Hits_Track.def if you know what you are doing, and make sure all the fields match the database fields, but the backup/resyc/copy is as fast and it's what I do when I need to make changes or think something got out of sync.
You are only operating on that specific table, without any automated processes.
The create table command will rebuild the indexes, etc. Then, do the 'defs' back up as indicated before resyncing, so you preserve the 'weights' in the Links and Category tables.
You can manually verify the Hits_Track.def if you know what you are doing, and make sure all the fields match the database fields, but the backup/resyc/copy is as fast and it's what I do when I need to make changes or think something got out of sync.
