Skip to main content

[SQL Server] How to Change the database server used for SST (formerly DSP)

Ben Bauer
  • Updated

NOTE: Customers who have their SST (formerly DSP) connected to the SKT (Syniti Knowledge Tier) will also need to perform some updates to that connection.  At this time, please open a ticket at support.syniti.com for assistance in updating the connection to reference the new database server

 

Follow this procedure to change the database server: 

  1. Stop the "CranSoft Service" SST Service(s) and IIS on the application server.
  2. Back up all the databases on the original database server.
  3. Restore those databases to the new database server.
  4. Create a login on the new database server for the SST app to use. Ideally this login will have the same name and password as the one already in use - if so this will make things easier.
  5. Assign that login to every database and give it dbowner privileges. (you might have to remove the original database user before doing this).
  6. On the application server, open the CranBerryConfigurator tool (in the \Web\Bin directory).
  7. For SST, the details only need to be changed once on the main Configurator page. On the right hand side, change the Server to the new server name, and the username and password to match the new login. Ensure that Connection Timeout is set to 60 and CommandTimeout is set to at least 300. Click Validate, and then Save. Skip steps 8 and 9 below and continue with step 10.
  8. For CranSoft (legacy product that came before SST), Expand Services and select the CranSoft Service. On the right hand side, change the Server to the new server name, and the username and password to match the new login. Ensure that Connection Timeout is set to 60 and CommandTimeout is set to at least 300. Click Validate, and then Save.
  9. Expand Sites, and Default Web Site and select the CranSoft virtual directory. Update the Server, username and password fields just as you did for the service and confirm that timeouts are set to appropriate values. Click Validate and then Save.
  10. Open SQL Server Management Studio, connect to the new database server and display the contents of the following tables (not all exist in CranSoft):
    1. CranSoft.dbo.DataSource
    2. CranSoft.dbo.DataSourceInstance
    3. DSPCommon.dbo.ttDataSourceRegistry
    4. DataGarage.dbo.dgTarget (specifically, the ConnectionString column)
    5. DataGarage.dbo.dgTargetSource (again, the ConnectionString column)
  11. Update values in these tables that refer to the old server name to the new server name. Also update username and password as appropriate.
  12. Start the "CranSoft Service" SST Service(s) and IIS. Log into the SST app. Navigate to System Administration / Configuration / DataSources and validate each datasource in turn, responding to any errors as appropriate.

The process overall is pretty straightforward and local client DBAs should be able to assist you with most of the initial steps.

Related articles