1. Home
  2. Knowledge Base
  3. On-premise/Customer-Hosted Server
  4. On-Premise Migrations
  5. Moving EIOBoard’s Database Only to a Different SQL Server

Moving EIOBoard’s Database Only to a Different SQL Server

  1. Make a backup.
    1. Option 1 – Use SQL Management Studio
      1. https://www.serverintellect.com/support/sqlserver/database-backup-ssmse/
    2. Option 2 – Using EIOBoard Admin
      1. Open up EIOBoard Server Admin
      2. Go to the SQL Tasks tab
      3. Edit the Backup Database job
      4. Confirm where it is being backed up to (@BackupLocation) and change it as needed
      5. Click Cancel or Save if you made changes to go back on the SQL Tasks tab
      6. Right click on the Backup Database job and say process now
      7. Look in the bottom left corner to follow the status of the job until it is complete
    3. Navigate to the location specified in the job and confirm the date/time of the file to make sure it is now
  2. Move the Backup and Restore.
    1. Copy the backup over to the new SQL server
    2. Restore the file using SQL Management Studio
      1. https://www.webhosting.uk.com/kb/how-to-restore-ms-sql-server-database-backup-file/
    3. If you do not wish to use the sa username and password, create a user in SQL with dbo (database owner) permissions
      1. https://docs.microsoft.com/en-us/sql/relational-databases/security/authentication-access/create-a-database-user?view=sql-server-2017
  3. Adjust Settings.
    1. Adjust EIOBoard Server
      1. Open EIOBoard Server Admin on your EIOBoard Server
      2. Right click on the EIOBoard Server Admin icon in the system tray and select Settings
      3. On the Database tab, change the Database Server, Database Name, Username, and Password to match your new server and login information.
    2. Adjust Both Web.config Files
      1. Open the EIOBoard Web folder (defaults to C:\Program Files\Savance\EIOBoard Server\EIOBoard)
      2. Locate and edit the web.config using notepad or equivalent
      3. Adjust this line to match your new server/login:
        <add key=”SQLConnection” value=”server=yourservernameorip;uid=yourusername;pwd=yourpassword;database=yourdatabase;Min Pool Size=7″/>
      4. Save that file and close it
      5. Go one folder deeper in the webservice folder and check if the Web Services has it’s own web.config
      6. If it does, adjust this line to match your new server/login:
        <add key=”ConnectionString” value=” server=yourservernameorip;uid=yourusername;pwd=yourpassword;database=yourdatabase “/>
      7. Save that file and close it
  4. Test it
  5. Decommission old SQL Server or Database.
    1. Either uninstall SQL Server from the location where it was originally installed, delete the database, detatch the database, or take the database offline to ensure that everything is pointing to the new database.
Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support