To relocate the Troika system, there are several key areas of the system that need to be moved and settings that may need to be amended to reflect the new location of the system. These notes are intended to highlight the areas for consideration and may not provide full details of the changes necessary on your own system.


Please consult your network and/or database administrator when planning a relocation of your Troika system. Ensure any new server meets our current System Requirements and is part of a supported operating model:
System Requirements - WealthWorks+ and Troika
Operating Models for Troika and WealthWorks+


Relocating the Troika System


These operations should be carried out by your database administrator (DBA). Please ensure you have up-to-date and verified backups before attempting to run any operations on your server. These notes are intended for guidance only and should not be relied on. Always seek advice from your DBA before completing any work on SQL Server.


Files and data to be moved:

  • SQL Server database,
  • Centrally located files and folders (master programs, release, documents, linked files, statutory forms and accounts),
  • WealthWorks+ (IIS virtual directory).


Settings which need to be reviewed after relocating the system:

  • 'TroikaSQL.ini' file for each user profile/workstation,
  • SQL Server security settings,
  • ODBC DSN connections for each user profile/workstation,
  • System Settings (Troika Utilities),
  • WealthWorks+ (IIS virtual directory),
  • Re-instate any SQL jobs on the new server.


The steps to relocate Troika should be following which are outlined below.


1. SQL Database - Backup the Current Database


  • Open SQL Management Studio.
  • Expand the console tree on the left-hand side of the console, and find the directory containing the 'Databases'.
  • Locate your Troika database from the list and right-click.
  • Select Tasks > Back Up...
  • Remove any existing entries shown in the Destination box.
  • Click on Add...
  • Using the ... button, navigate to the required location of the backup file, and name appropriately.
  • Click OK, then OK to revert to the back-up screen.
  • Navigate to the Media Options page, ensuring the 'Overwrite media' option says 'Overwrite all existing backup sets' and not 'Append to the existing backup set'.
  • Click OK to start the backup.
  • Once completed the file will be available in the directory chosen. Ensure this location is accessible from the new server.


2. SQL Database - Restore the Backup to a new Database


  • Open SQL Management Studio.
  • Expand the console tree on the left-hand side of the console, and find the directory containing the 'Databases'.
  • Right-click on 'Databases' and select 'Restore Database...'.
  • Select 'Device' and using the ... button, then Add, navigate to the location of the .bak backup file taken from the current server.
  • Click OK, then OK to revert back to the restore screen.
  • Edit the database name if not already populated, to TROIKA.
  • NB Ensure you are using a unique database name on this server, so you do not overwrite existing live databases.
  • Click on the Files page and check the two file name paths are correct. They should point to a new data file (TROIKA_DATA.MDF) and a new log file (TROIKA_LOG.LDF).
  • Once these are checked, click on OK to begin the restore process.


3. Review SQL Server security


Once the database has been restored, you may need to review or re-establish the SQL security settings for this database and grant access for SQL or Windows User accounts to connect this database with the appropriate ‘db_TR_USER' or 'db_TR_SQL_ADM' roles. The ODBC DSN connection from each user profile or workstation will require access to this new database using either SQL or Windows authentication. Ensure the correct application pool account and the network service account access is grant to the database for WealthWorks+ to operate.


4. Workstation of User Profile - Amending/Creating New Database Connection


From the user workstation or for the user profile (for terminal server/Citrix users), you will need to create a new ODBC data connection to the new database. Alternatively, you can amend the existing DSN to point to the new SQL Server and database.


If the DSN is amended, the revised connection will need to be re-selected from the Troika Desktop from each user profile, or workstation.


Ensure you have up-to-date SQL Server drivers before proceeding. Please check with thewealthworks if you are unsure of the correct driver version.


You can find the 'Set up ODBC data sources (32-bit)' option in the Control Panel of the workstation.


In the event your organisation is utilising a 64-bit version of Microsoft Office, please refer to the following for further instructions on setup:
Installing Troika on Operating Systems Requiring 64-bit Microsoft Office

You will need to add a 'System DSN' and you will also be asked for a SQL Server username and password to complete the connection. Please note that you can use SQL or Windows Authentication to connect to the SQL Server database. If using SQL authentication, all users must use the same SQL Server user name and the SQL user must have the 'db_TR_USER' role for the Troika database. If a windows user account is being used, the account must also have the 'db_TR_USER' role for the SQL database.


The language of the DSN must also be set to English, and not US or British English. Check the default language of the SQL or Windows account on the SQL Server is set to English before creating the DSN for the user account or profile. This can be found in the properties of the user account in SQL Management Studio.


Use the following settings to create an ODBC data connection to the database.


  • Microsoft SQL Server ODBC Driver Version
  • Data Source Name: <Your Database Name>
  • Data Source Description: <Your Database Name>
  • Server: <Your Server Name>
  • Database: <Your Database Name>
  • Use ANSI Quoted Identifiers: Yes
  • Use ANSI Null, Paddings and Warnings: Yes
  • Use Failover Server: No
  • Language: (Default)
  • Data Encryption:  No
  • Translate Character Data: Yes
  • Use Regional Settings:  No
  • Log Long Running Queries: No
  • Log Driver Statistics: No


After configuring the System DSN, you will need to use the test option to check for successful connection to your database.


5.  Workstation or user profile - Selecting the new connection.


After amending the existing connection or creating the connection, it must then be selected from the Troika Desktop.


  • Double click on the Troika Desktop icon to start the application running in the system tray.
  • In the event of warnings indicating a lost ODBC connection, select suitable responses to continue to open application.
  • Select the new ODBC DSN connection either:
    • by right clicking on the Troika Desktop in the System Tray, selecting 'DSN', then ‘Select DSN’. Select the new ODBC connection to new SQL database and click OK.
    • by clicking 'Tools' on the Troika Desktop, selecting 'DSN', then 'Select DSN'. Select the new ODBC connection to the new SQL database and click OK.
  • NB  You may need to enter the SQL login details again at this point, to confirm the connection.
  • Check the Troika Desktop displays the correct SQL Server and database. For example:


The new database connection will need to be selected for each user workstation or profile accessing Troika.


6. Moving Centrally Located Files and Amending the 'TroikaSQL.ini' Configuration File


A number of shared areas store files required by Troika to generate accounts and documents. If these are also to be relocated to a new server, backup the entire contents of these folders and migrate these to their new locations. The paths to these locations are stored in the 'TroikaSQL.ini' configuration file, and within the Troika database.


From the Troika Desktop icon in the system tray, right-click and select ‘About’. Click in the link to open the default 'TroikaSQL.ini' in Notepad. It may be necessary to review the following entries in this file:


  • AccountPath=\\SERVERNAME\TWWDATA\Accounts - Amend this entry to reflect the new location for the accounts. For example, ‘\\NEWSERVERNAME\TWWDATA\Accounts’. Ensure you have copied the entire contents of the original 'Accounts' folder and its sub-folder structures to the new location.
  • WorkfilePath=\\SERVERNAME\TWWDATA\Forms - Amend this entry to reflect the new location for the forms. For example, ‘\\NEWSERVERNAME\TWWDATA\Forms’. Ensure you have copied the entire contents of the original ‘Forms’ folder and its sub-folder structures to the new location.
  • troikmaster=\\SERVERNAME\TWWDATA\Master\FpsTroik.mdb - Amend this entry to reflect the new location of the master versions of Troika programs. For example, ‘\\NEWSERVERNAME\TWWDATA\Master’. Ensure you have copied the entire contents of the original ‘Master’ folder and its sub-folder structures to the new location.


Save and close the file.


From Troika Utilities, System tab, select the System Settings menu option. Highlight the File / Path Location option, and amend:


The file path for linked documents, and the default location for word template files.

DocLinkLocation \\NEWSERVERNAME\TWWDATA\Forms


Exit Troika.


7.  WealthWorks+


From the server running Internet Information Services (IIS), open IIS Manager, and select the WealthWorks+ virtual directory. Revise the connection string in the ASP.NET configuration area of the virtual directory to connect to the correct SQL Server and database.


If WealthWorks+ is being moved from the existing server, to another server running IIS, please follow the existing ‘new installation’ instructions, provided with your current release of WealthWorks+.


Once installed on the new server, access Troika Utilities, System tab and the System Settings menu option. Highlight the WealthWorks+ System Settings option, and amend:


The WWPLUSURL entry to show the correct URL for WealthWorks+. For example:

http://<NEWWEBSERVERNAME>/WealthWorksPlus


8.  SQL Jobs


Re-instate any SQL maintenance jobs set-up on the original server, adding these, as required, to the new SQL Server.


Additional assistance on the Daily and Weekly jobs can be found here, if required:

Wealthworks+ Release - Ensure SQL Server Maintenance Jobs are Present


Further information on SQL maintenance plans, including backups of the SQL database, can be found here:

Backup and Maintenance Requirements of the SQL Database


These notes were last reviewed 03/2024.