• State Verified Answer
  • Replies 5 replies
  • Subscribers 434 subscribers
  • Views 1733 views
  • Users 0 members are here
Options

How to reset TM segment numbering to 1

Stepan Konev

Hi mates,
Accidentally, I Batch Delete'd all segments from my TM. Thank God, I saved a tmx copy just before 'testing' the Batch Delete feature. I imported it back and it seems to be ok but for one slight problem: segment numbering in TM now starts from the next to previous last number. Roughly speaking, I had 50,000 segments, now the first segment number is 50,001, then goes 50,002, etc.
Is there any way to reset segment counting to start from 1 again, either internally or with use of apps?
Cheers
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0

    Hi  ,

    I think the only way to handle this is to recreate the TM by importing your TMX into an empty TM. I think when you import to the new one the missing TUs are added to the end with the next available number. We don't fill gaps... which sort of makes sense since we don't match the content to the ID anyway so wouldn't necessarily know which TU to put against which ID.

    Out of interest why is this important for you?

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0

    Thank you Paul. I see. Ok, that's what I am going to do now.

    Not to say that it is very important for me, but it looks pretty weird... mess... don't know. I ended up with the last segment number in TM is 2 times the actual number of segments. A bit confusing. Besides, this is a GroupShare TM. Now I have to figure out how I create a substitute TM with minimum aftermath. Most probably I would just leave it as it is now.
  • 0 in reply to Stepan Konev
    TM is a database... i.e. deleting a record only marks the record as deleted... until the database is compacted.
    So it should be enough to make the database perform the compacting, which, I believe, is what "reorganizing" the TM does.
  • 0 in reply to Evzen Polenka
    I think that might do it Evzen... but actually there isn't a "reorganise" feature for a TM in Studio. You can reindex and recompute but neither will achieve what Stepan wants. I also tried "compact" in a SQL editor but that didn't do the job either. The only ways I know, and both work for me are to create a new TM and import the TMX or use the Upgrade TM feature which essentially automates the import of a TMX into a new TM.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul
    @Evzen Polenka: thank you for your suggestion anyway.

    Ok, then one more question: if I create a new empty TM (as suggested by Paul) with exactly the same properties (location, container, filename, etc.) to replace the older one, will other users receive a 'red-cross' message stating that the_older_TM could not be found and will they have to re-add the newly created server-based TM? Or will the new server-based TM be enabled 'silently' / without any sign in lieu of the older one?