• State Not Answered
  • Replies 3 replies
  • Subscribers 69 subscribers
  • Views 98 views
  • Users 0 members are here
Options
Related

how to update the database when the server is migrated

charleneforbes

Hi,

I'm having trouble logging in to the support portal so hoping I can ask here.  Just a quick question, our SQL database admins are planning to migrate the cluster on to a new server.  Is it just a case of updating the database connection in the Configuration Center when the work is done?

Thanks

Charlene

  • 0

    We are planning to migrate our SQL database cluster to a new server, and I would like to understand the steps required to ensure everything continues working properly after the migration. Our SQL database administrators will be handling the server-side work, but I am not entirely sure what needs to be changed on the application side. My first thought was that updating the database connection details in the Configuration Center might be enough, but I would appreciate confirmation from anyone who has completed a similar migration.

    Before making any changes, I assume it is important to verify that the database has been migrated successfully and that all the required data, users, permissions, and stored procedures are available on the new server. We would also need to confirm the correct server name, database name, authentication method, and connection settings. If the application uses a specific service account or encrypted connection, those details may need to be checked as well. I would prefer to understand the complete procedure beforehand rather than risk an unexpected interruption when the application tries to connect to the new database.

    Has anyone experienced this type of SQL database migration and can explain whether changing the connection settings in the Configuration Center is sufficient, or whether additional steps are necessary? For example, do we need to restart any application services, update other configuration files, or verify the connection through a separate test? I would appreciate any practical advice on the recommended migration sequence, including what should be checked before switching over and how to confirm that the application is functioning correctly afterward. Thanks in advance for sharing your experience and recommendations.

  • 0 in reply to georgesalazar789

    Hello, the below steps are from KB article "Migrate the Microsoft SQL Active Roles databases" (000004980)

    HOW TO: Migrate the Microsoft SQL Active Roles databases

    And once your support portal is restored, there is another KB article to review: SQL settings for Active Roles performance (000016273)

    Recommended SQL settings for Active Roles performance

    You can submit a general case here to have your access restored:

    https://support-user.oneidentity.com/s/submit-case

    From KB000004980, to migrate the DB:

    Summary
    HOW TO: Migrate the Microsoft SQL Active Roles databases
    Problem Description

    It might be necessary for performance, capacity, or supportability reasons to migrate the Active Roles SQL Configuration and/or Management History databases from the existing SQL host to a new one.

    NOTE: If SQL Database replication is enabled, it will be necessary to break replication, delete all subscribers, and demote the Publisher before proceeding with the below steps, as mixed SQL versions are not supported within a SQL Replication Group.

    After the below steps have been completed, SQL Replication will need to be reconfigured from scratch.

    Resolution
    1. Open the Active Roles Configuration Center. On the Administration Service tab, under the Active Roles databases section, note the current Active Roles Service Account, Active Roles Admin Group, and the Configuration and/or Management History database server and database names.
    2. Stop the Active Roles Administration Service on all Active Roles Administration Service hosts.
    3. In SQL Server Management Studio on the current Microsoft SQL Server host, back up the noted database(s) to disk. For assistance with backing up the databases please see this Microsoft resource.
    4. Copy the database backup files to the target Microsoft SQL Server host or to a network location accessible from that host.
    5. In SQL Server Management Studio, create a new Configuration database and restore the backup. Repeat for the Management History database if a separate database is used. For assistance with restoring a database please see this Microsoft resource. 
    6. Ensure that the necessary permissions for the Active Roles Service Account are added to the new SQL instance. db_owner and/or sysadmin should be sufficient.
    7. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\One Identity\Active Roles\Configuration\Service   
    8. Set the Configured DWORD value to 0.
    9. Close and then reopen the Active Roles Configuration Center.
    10. On the Dashboard tab, under the Administration Service, click on Configure
    11. Specify the Service Account which was previously noted in the Active Roles Configuration Center in Step 1 above. Click Next.
    12. Specify the Active Directory Group granted the Active Roles Admin Role which was previously noted in the Active Roles Configuration Center in Step 1 above. Click Next. 
    13. On the Database Options screen, choose to use an Existing Active Roles database and click Next.
    14. Specify the new SQL Server host and the configuration database name. Click Next and Change, then Finish.
    15. The Active Roles Administration Service will need to be restarted. Choose Restart now in the prompt which appears in order to continue.
    16. If Management History is stored in a separate database, choose the Change button in the Active Roles database section.
    17. Check the box labeled Store management history data in a separate database (advanced) and click Next.
    18. Choose to use an Existing Active Roles database and click Next.
    19. Specify the SQL Server and database name of the new Management History database and click Next and Change, then Finish.
    20. The Active Roles Administration Service will need to be restarted. Choose Restart now in the prompt which appears in order to complete the process.
  • 0 in reply to richard lambert

    HI, thanks for that, I managed to email support and get my account restored. Their advice was similar; essentially migrate the database with all the same permissions, redo the connection with configuration manager, then restart the Active Roles admin service.