How to change Trados GroupShare 2017 SR1 database configuration

Article Number:000006263 | Last Updated:3/7/2022 1:40 PM

Scope/Environment

Trados GroupShare 2017 SR1

Symptoms/Context

You have installed a Cumulative Update Trados GroupShare 2017 and you observe that no Translation Memories are listed in the Web UI under Resources.
When you check under System Configuration > Containers you also do not get listed your Translation Memory Container.

This article describes how to change the database configuration used by Trados GroupShare 2017 (SR1), e.g. when in need to move to a different Microsoft SQL Server instance.

Resolution

Please follow the below steps to change the location of each database used by Trados GroupShare 2017 SR1:

Stop all services starting with SDL on the Trados GroupShare application server.
Launch the Trados GroupShare Console on the Trados GroupShare application server.
Go to Console Root > SDL Trados GroupShare > Databases.
Adjust the Database Location values in sections GroupShare System Database and MultiTerm Master Database to reflect the new Microsoft SQL Server instance and click Apply Changes.
Open the configuration file(s):
- appsettings.json located in C:\Program Files (x86)\SDL\SDL Server\Management and
  ...in a text editor application adjust the "GsConnectionString" attribute value of the following lines to your new Microsoft SQL Server address:
```
"GsConnectionString": "data source=<your_sql_server_address>;initial catalog=[SDLSystem DATABASE NAME];integrated security=True;connect timeout=30;multipleactiveresultsets=true"
```
  NOTE: The appsettings.json is only required to be changed as of Trados GroupShare 2017 SR1 CU8.
Open the configuration file(s):
- Sdl.TranslationModelService.Builder.exe.config located in C:\Program Files\SDL\SDL Server\TranslationModelService\ and
- Sdl.TranslationModelService.Host.exe.config located in C:\Program Files\SDL\SDL Server\TranslationModelService\
  ...in a text editor application and in each file adjust the data source attribute value of the following lines to your new Microsoft SQL Server address:
```
<add name="modelDatabase" connectionString="data source=<your_sql_server_address>;initial catalog=<servername>_TMModel;integrated security=True;connect timeout=30" />
```
Open the configuration file(s):
- Sdl.TMService.Agent.exe.config located in C:\Program Files\SDL\SDL Server\TMService\ and
- Sdl.TMService.Host.exe.config located in C:\Program Files\SDL\SDL Server\TMService\ and
- Sdl.LanguageResourceService.Host.exe.config located in C:\Program Files\SDL\SDL Server\LanguageResourceService\
  ...in a text editor application and in each file adjust the data source attribute value of the following lines to your new Microsoft SQL Server address:
```
<add name="systemDatabase" connectionString="data source=<your_sql_server_address>;initial catalog=<servername>_TMService;integrated security=True;connect timeout=30" />
```
Open the configuration file(s):
- Sdl.GroupShare.WebHooksService.exe.config located in C:\Program Files\SDL\SDL Server\WebHooks Service\
  ...in a text editor application and in each file adjust the data source attribute value of the following lines to your new Microsoft SQL Server address:
```
<add name="MS_SqlStoreConnectionString" connectionString="data source=<your_sql_server_address>;initial catalog=<servername>_WebHooks;integrated security=True;connect timeout=30" providerName="System.Data.SqlClient" />
```
Edit each [dbo].[DatabaseServer] table in your Translation Memory (TM) Service and TM Model databases and adjust the values for the column [ServerName] to your new Microsoft SQL Server address (please see Microsoft Server SQL databases used by Trados GroupShare 2017 and 2017 SR1 for details on how to identify your TM Service database).
Restart all previously stopped SDL services.
- How to restart the Trados GroupShare 2017 (and higher) Services

Root Cause

Reference

Send Article Feedback