Server and Database Migration

Server and database migrations typically take place because more capacity is needed or the hardware can no longer meet the requirements and an update is not possible. If after initial installation the DEACOM databases need to be moved, there are several key steps to take to ensure all data is protected and the transition goes smoothly. Refer to the section below based on the migration being considered. Any technical support assistance needed to migrate is a billable project.

Moving DEACOM databases to a new location on the same server

  1. Backup all databases.
  2. Detach the databases.
  3. Move the databases to the new drive or folder on the server.
  4. Reattach the databases.
  5. Change the database default locations under Server Properties > Database Settings to point to the new location.

Moving DEACOM databases to a new server

  1. Install the same or a newer version of SQL Server Management Studio on the new server with mixed mode authentication and enable Filestream during installation.
    • If skipped during installation, both mixed mode and Filestream can be configured afterwards.
    • Confirm SQL is properly licensed or a trial version will stop working after a given number of days, preventing DEACOM from running.
  2. Login to the current DEACOM environment from the new SQL Server so that the server is whitelisted.
  3. Confirm firewall settings are configured to allow remote access to SQL Server.
  4. In SQL Server Management Studio:
    1. Expand the Security folder, then right-click on the Logins folder and select "New Login".
    2. Setup a login for deacom where the password matches exactly what is currently on the old server. Contact DEACOM Technical Support to setup an account if you do not know the password.
    3. Navigate to Server Roles and check the "public" and "sysadmin" flags. If desired, companies may use another login, with the "sysadmin" flag checked, for running installs and updates. In this case, the "sysadmin" flag does not have to be checked for the "deacom" login. If the "deacom" user in not set as "sysadmin," users will be required to enter the appropriate SQL credentials when running DEACOM updates.
    4. Click "OK" to create the login.
  5. Confirm protocols are enabled in SQL Server Configuration Manager.
    1. Click "Start" on the computer, and open the Control Panel.
    2. Select Administrative Tools, then Computer Management.
    3. Expand "Services and Applications".
    4. Expand "SQL Server Configuration Manager".
    5. Expand “SQL Server Network Configuration”.
    6. Click “Protocols for MSSQLSERVER”.
    7. Right-click on “TCP/IP” and select “Enable”.
    8. A warning will appear indicating that the service will have to be restarted. Click "OK".
  6. Copy the DEACOM folders to the new server.
  7. Modify the DEACOM ini file to point to the new SQL Server or server\instance per SQL installation.
  8. Backup existing databases.
  9. Restore existing databases.
  10. Set the owner of the database.
    1. Right-click each database and select Properties.
    2. Under Files, click "…" and make SQL deacom security login the owner of the database.
    3. If updating SQL, compatibility level may also be checked under Options.
  11. Run the current DEACOM update against the new environment. Important: Ensure the Automation and Web Services are stopped if they have been previously installed.
  12. Install or start the Automation Service.
  13. Install or start the Web Services.
  14. Confirm or modify the existing Trigger and EDI setup to reflect the new server.
    • Re-save all Triggers to update them with the new server information.
  15. Test all functionality, including EDI, before final cut-over.
  16. Repeat steps 6-15 for final cut-over to capture any changes since initial testing.
  17. Detach databases from the old server so they are no longer accessible.