• State Verified Answer
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 6787 views
  • Users 0 members are here
Options
Related

What is the TM size limit in MBs/GBs and/or TUs, in Studio 2017?

Michael Beijer

Think I asked somewhere recently, but can't remember. What is the maximum TM size in MBs/GBs and/or TUs, in Studio 2017? IN DVX£, e.g., it is 2GB per individual file, due to constraints of the underlying database system.

 

Michael
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    What are you talking about Michael? 2GB would be around the limit for a filebased Multiterm termbase as this is essentially MSAccess. But an SDLTM is SQL and this is a different story. I don't know what the limit is here, but I reckon it's probably going to be capped by performance. I have seen translation memories in excess of 2GB, but they are rare as this is getting ridiculously large and not likely for a Freelance translator unless they are importing TMs collated from wherever they can find them.

    And if you talk about server it's a different story again as the capacity is much increased.

    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
    Just wondering what the largest TM is Studio 2017 can handle.

    I have a very large EU-related TMX collection (courtesy of farkastranslations.com/eu_translation_memories.php), and I was wondering how much of it I could squeeze into Studio 2017 TMs.

    The reason I want to do this is I am playing around with various ways of pre-translating all my projects against my massive TMX database before translating them in my CAT tool. Just in case there are useful segments somewhere in my huge collection.

    So the idea isn't to have it all connected when actually translating (which would obviously be insane), but to just be able to access the entire database to pre-translate my project with.

    I basically create a special project just for pre-translating my new projects, import the documents I want to translate, and pre-translate the documents against the massive database. I then export the results as a TMX, and then connect only this TM when actually translating.

    I could for example run the pre-translation step in memoQ, or Studio (as they both support very large TMs/TM collections), and do the actual translation in another CAT tool.

    Michael
  • 0 in reply to Michael Beijer
    PS: I didn't remember/know that SDLTMs are SQL-based. That's great news.

    My TMLookup database (which is based on SQlite), is around 40,000,000 TUs. Just for shits and giggles, I'm trying to find a way to pre-translate my docs using a TM/TM collection of this size. ;-)
Reply Children