MOVING DATABASES TO THE NEW SERVER

This topic covers the process of migrating the databases to the new server, which includes recreating the client logins, running scripts, and editing app settings.

click to open PDF 

 

 

STOP DATABASE CONNECTIONS ON THE NEW SERVER

  1. Ensure System Galaxy software, idProducer web client (browser) and Print Dispatcher are not running.

  2. On the new server, you must stop the following services ...

    • GCS WebAPI service

    • GCS ClientGW service

    • GCS Comm service

    • GCS DataLoader service

    • GCS DBWriter service

    • GCS Event service

    • GCS (and any other GCS service)

      Notate which other services you stopped.

    • idProducer Connector service

    • idProducer Server service

    • IIS Service

    • System Galaxy software application

     

     

     

  3. Open the Services window by typing “Services” into the Search field of the Windows Taskbar.  

    A screenshot of a computer Description automatically generated

    Services window showing all Galaxy services

     

  4. Right-click the name of the service and choose ‘STOP’ from the shortcut menu.

  5. Do this for every service listed above.

 

 

 

LAUNCH SQL SERVER MANAGEMENT STUDIO ON THE NEW SERVER

 

  1. Move a copy of all the database .bak files into the SQL Server Backup folder on the new server.

    PATH $:\Program Files\Microsoft SQL Server\MSSQL15.GCSSQLEXPRESS\MSSQL\Backup

     

  2. Launch the SQL Server Management Studio and login to the System Galaxy SQL instance. 

    1. Select Database Engine for Server Type.

    2. Select the correct Server Name
      (machine_name\instance_name)

    3. Select SQL Server Authentication type.

    4. Enter the “sa” login and password.

    5. Click Connect to connect to the GCSSQLEXPRESS instance and its databases.

       

      A screenshot of a computer Description automatically generated

      SQL Server Mgt Studio > Login window

       

     

 

 

 

DELETE THE BLANK DATABASES FROM THE GCS SQL INSTANCE

 

 

  1. Under the GCSSQLEXPRESS instance, expand the Databases branch.

  2. Delete the following databases from the database branch as follows…

    • SysGal,

    • SysGalArc

    • idProducer

       

    1. Right-click each database name and select Delete from the shortcut menu. 

      A screenshot of a computer Description automatically generated

      SQL Server Mgt Studio > Object Explorer

       

    2. Click the OK button to confirm the deletion, as needed.

      A screenshot of a computer Description automatically generated

      SQL Server Mgt Studio > Deleting Database Object

       

    3. Repeat these steps for all 3 databases separately ( SysGal, SysGalArc and idProducer).

       

     

 

 

 

 

RESTORE BACKUP DATABASES ON THE GCS SQL INSTANCE

This section covers restoring the backup databases that you copied into the MSSQL Backup folder ( SysGal, SysGalArc and idProducer).

 

  1. Right-click the Databases branch name and select “Restore Database…” from the menu option.

    A screenshot of a computer Description automatically generated

    SQL Server Mgt Studio > Object Explorer

     

  2. Select the General tab of the Restore Database screen …

  3. Click the Device radio button in the Source section of the page.

  4. Click the Browse [ … ] button to browse to the MSSQL Backup folder .

     

    A screenshot of a computer Description automatically generated

    SQL Server Mgt Studio > Restore Database: General page

     

  5. Click the Add button to open the Backup folder. 

    Graphical user interface Description automatically generated

    Restore Database General > Add Devices

     

  6. Select (highlight) one database filename that you want to restore (i.e., sysgal, sysgalarc, idproducer).

    A screenshot of a computer Description automatically generated

    Restore Database General > Select Backup file

     

  7. Click OK to select the bak file. 

  8. Click OK to add the Backup folder.

    NOTE: the backup path (shown here) is the MSSQL15 backup path on the local server for
    SQL Server v2019.  Your backup path could vary but should display correctly in this screen. 


    Graphical user interface Description automatically generated

    Restore Database General > Add Backup Path

     

  9. When you return to the General page, the fields should be populated as follows …

    • Under Source, the Device field should display the backup path to the database files.

    • Under Destination, the Database field should display the database name you chose.

     

  10. Verify the Restore checkbox (is “check”) in the Backup Sets list-view.

  11. Click the OK button to restore the selected database.

    A screenshot of a computer program Description automatically generated

    Restore Database > General page: showing the Full Database Backup is selected

     

     

  12. Click the OK button to confirm the successful restoration.

    A computer screen with a box and a box with a button Description automatically generated with medium confidence

    Restore Database Files > Confirmation message

     

  13. Repeat these same steps to restore the other databases (sysgal, sysgalarc, idproducer).

  14. Refresh the entire SQL Instance branch when you are finished restoring all the databases.

 

 

 

 

MANUALLY DELETE THE GCS USER LOGINS ON THE NEW SERVER

You must delete the Galaxy client logins for each database branch (i.e., sysgal and sysgalarc).

 

  1. (SysGal) Delete the GCS User Logins for the SysGal database as follows …

    1. Expand the SysGal database that is under the Databases branch.

    2. Expand the Security>Users branches and delete GCS User Logins as follows:

    3. Right-click the “gcs_client” and choose Delete from the shortcut menu.

    4. Right-click the “gcs_web_client” and choose Delete from the shortcut menu.

       

  2. (SysGalArc) Delete the GCS User Logins at the SysGalArc database as follows …

    1. Expand the SysGalArc database that is under the Databases branch.

    2. Expand the Security>Users branches and delete GCS User Logins as follows:

    3. Right-click the “gcs_client” and choose Delete from the shortcut menu.

    4. Right-click the “gcs_web_client” and choose Delete from the shortcut menu.

       

  3. Refresh the Databases branch and verify both logins are removed from the databases.

    1. (SysGal) Under SysGal’s Security>Users branch, verify both logins (gcs_client & gcs_web_client) are removed (not visible in the list of logins).

    2. (SysGalArc) Under SysGalArc’s Security>Users branch, verify both logins (gcs_client & gcs_web_client) are removed (not visible in the list of logins).

 

 

 

 

MANUALLY RECREATE GCS USER LOGINS ON THE NEW SERVER

 

  1. Recreate the gcs_client logins as follows …

    1. Expand the Security>Logins branch that is under the GCSSQLEXPRESS instance.

    2. Double-click on the gcs_client login. This will open the Properties screen.

       

      A screenshot of a computer Description automatically generated

       

    3. In the Properties screen, select the User Mapping screen

    4. Choose (“check”) the SysGal database and enter “dbo” in the Default Schema field

    5. Enable (check) the db_backupoperator, db_datareader, and db_datawriter and public.

    6. Click OK to recreate the GCS User Login. The client login will be added to the chosen database.

      A screenshot of a computer Description automatically generated

       

    7. Repeat Step-1 to recreate the gcs_client login for the SysGalArc database.

       

  2. Recreate the gcs_web_client logins as follows …

    1. Expand the Security>Logins branch that is under the GCSSQLEXPRESS instance.

    2. Double-click on the gcs_web_client login. This will open the Properties screen.

      A screenshot of a computer Description automatically generated

       

    3. In the Properties screen, select the User Mapping screen

    4. Choose (“check”) the SysGal database and enter “dbo” in the Default Schema field

    5. Enable (check) the db_backupoperator, db_datareader, and db_datawriter and public

    6. Click OK to recreate the login. The client login will be added to the chosen database.


      A screenshot of a computer Description automatically generated

    7. Repeat Step-2 to create the “gcs_web_client” for the SysGalArc database.

       

  3. Proceed to Running the License Script on the idProducer database.

 

 

 

RUN THE IDPRODUCER LICENSE (SQL STATEMENT)

This topic explains how to reset the idProducer license to “null”. This must be done so that the license can be recreated when the system is re-registered in a later step. 

ASSUMPTION ...

  • You must have already successfully restored the backup file for the idProducer database.

 

  1. Open the SQL Server Management Studio (SSMS) and sign-in using SQL Authentication and “sa” login.

  2. Expand the “Databases” branch in the SSMS Object Tree.

  3. Right-click on the “idProducer” database name and choose New Query… from the shortcut menu.

    RESULT: a blank Query tab will open.

     

  4. Enter (or copy/paste) the SQL statement (below) and click Execute toolbar button.

    sql must use exact syntax:

    update idProducer.dbo.Subscription set License = null where SubscriptionID = 1000

     

    A screenshot of a computer Description automatically generated

    SQL Server Mgt Studio > SQL Query tab

     

  5. To confirm your license is null, you can run the following SQL Statement on the idProducer database:

    sql must use exact syntax:

    select [SubscriptionID], [CompanyName], [License] FROM [idProducer].[dbo].[Subscription]

     

    RESULT: the License column should be “null” for SubscriptionID 1000

     

  6. Close the Query tab without saving. And the SSMS window.

  7. Continue to the next section for Upgrading System Databases.