Articles in this section

Migrating BoringBase Database to a New SQL Server

  • Updated
Follow

Overview

This document provides step-by-step instructions for migrating the BoringBase database to a new SQL Server. To maintain proper functionality, the BoringBase database must reside on the same SQL Server as the Milestone Surveillance database.

 

Prerequisites

  • SQL Server Management Studio installed
  • Access to both source and destination SQL Servers
  • Appropriate permissions to perform backup and restore operations
  • Sufficient disk space on the destination server

 

Important Notes

  • The BoringBase database must be migrated to the same SQL Server instance that hosts the Milestone Surveillance database.
  • No manual configuration of connection strings is required, as Boring automatically retrieves the SQL Server address from the Milestone registry settings.

 

Migration Steps

1. Create Database Backup

  1. Open SQL Server Management Studio
  2. Connect to the source SQL Server instance
  3. In Object Explorer, expand the Databases node
  4. Right-click on the BoringBase database
  5. Navigate to Tasks Back Up
  6. In the Back Up Database window:
    • Set backup type to "Full"
    • Choose "Disk" as the backup destination
    • Click "Add" to specify the backup file location
    • Enter a meaningful name for your backup file (e.g., "BoringBase_Backup_YYYYMMDD.bak")
    • Verify the backup destination path
  7. Under Options:
    • Select "Verify backup when finished" for additional validation
    • Choose an appropriate compression option
  8. Click OK to start the backup process

 

2. Transfer Backup File

  1. Locate the backup file created in step 1.
  2. Transfer the backup file to a location accessible by the destination SQL Server.
  3. Ensure sufficient permissions are set on the backup file for the SQL Server service account.

 

3. Restore Database on New Server

  1. Open SQL Server Management Studio
  2. Connect to the destination SQL Server instance
  3. In Object Explorer, right-click on Databases
  4. Select "Restore Database"
  5. In the Restore Database window:
    • Enter "BoringBase" as the destination database name
    • Select "Device" under Source
    • Click the browse button (...) to locate your backup file
    • Select the backup file transferred in step 2
  6. Under Options:
    • Verify the restore locations for data and log files
    • Choose appropriate options for existing connections
  7. Click OK to begin the restore process

 

4. Post-Migration Steps

  1. Re-install Boring Server Complete on the Milestone management server
  2. Verify that Milestone is properly configured to use the new SQL Server instance
  3. Test the connection to ensure Boring can access the migrated database
  4. Monitor system logs for any potential errors

 

Verification

After completing the migration, verify the following:

  • Boring Server can connect to the database
  • All historical data is accessible
  • System functions operate normally
  • No connection errors appear in the system logs

 

Troubleshooting

If you encounter issues after migration:

  • Verify that the Milestone Surveillance database and BoringBase are on the same SQL Server instance
  • Check SQL Server connection logs for any authentication issues
  • Ensure the SQL Server service account has appropriate permissions
  • Verify that the Boring Server service is running

 

Note: Always perform a test migration in a non-production environment first if possible. Create additional backups of both databases before beginning the migration process.

Comments

0 comments

Please sign in to leave a comment.