A Server-Based Translation Memory was deleted by accident or a Batch Delete task was performed in Trados Studio that deleted content from the Server-Based Translation Memory.

You have a backup of the Trados GroupShare databases (see Microsoft Server SQL databases used by Trados GroupShare) and want to restore the Translation Memory data.

Translation memory data is stored in Translation Memory container databases. However, the translation memories are also referenced in the Trados GroupShare system database (see Microsoft Server SQL databases used by Trados GroupShare). Therefore, the Translation Memories will not be visible in Trados GroupShare if your restore only the Translation Memory container database to the state before the Translation Memory was deleted. Worse, if any Translation Memory properties have changed, inconsistencies between the Trados GroupShare system database and the container database may lead to errors.
Attaching a previous version of the container under a different name is not be possible since duplicated Translation Memories names are not permitted.
 

Workaround A: Restore the Translation Memory from a .tmx file

Because of above mentioned restrictions, it may be easier to restore the Translation Memory by importing an existing .tmx backup into a new (or the old) Translation Memory. If you do not have a .tmx backup, refer to below solutions.

Workaround B: Attach Translation Memory Container to a different Trados GroupShare instance

Note: Below solution requires SQL Server knowledge. Steps 1-2  should be applied by your database administrator.

This solution can only be applied if

• have access to a second Trados GroupShare instance and
• none of the Translation Memories in the Translation Memory container have a name identical to any Translation Memory on the second Trados GroupShare instance.

1. Restore the Translation Memory container database to the SQL instance used by the second Trados GroupShare instance
2. In this database, grant db_owner role to the login used by Trados GroupShare
3. Log into the Trados GroupShare web interface
4. Go to Infrastructure
5. Activate tab Containers
6. Add a new container with Database Name equal to the name of the database restore in step 1
7. Go to Translation Memories
8. Export the relevant Translation Memory of the backup container
9. Import the .tmx data into the translation memory on the first Trados GroupShare instance

Note: Some customers who are in the North/South America regions and are using versions of Trados GroupShare older then 2020 SR1 CU4 may run into the issue described in this article.

 

Do you still require help?

If this article has not solved your issue or if you require assistance, contact the SDL Support Team:

• For customers holding a support contract:
  1. Log in to the SDL Gateway with your SDL Account.
  2. Click on the blue Log a Case
     button. Note: For detailed instructions, refer to the video tutorial.