Database migration to a new SQL Server

Version 7

    Verified Product Versions

    LANDESK Management Suite 9.5LANDESK Management Suite 9.6LANDESK Management Suite 2016.x

    Migrating a database is a pretty straightforward process and is well documented on TechNet and other outlets. Here is a list of instructions you can use to migrate a SQL database from one server/host to another.

     

    1. Build or install new SQL server.      Install SQL Server 2012 from the Installation Wizard (Setup)
           http://msdn.microsoft.com/en-us/library/ms143219.aspx
    2. Use the following directions to backup your database and restore it on your new SQL server:
           http://technet.microsoft.com/en-us/library/ms187048.aspx
    3. If the database is a new install, you'll want to verify that Mixed-mode login is enabled on the SQL server. The how-to for that is found here Change Server Authentication Mode and is posted below in case the link stops working.

     

    Using SQL Server Management Studio to change authentication mode

     

    1. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.
    2. On the Security page, under Server authentication, select the new server authentication mode, and then click OK.
    3. In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.
    4. In Object Explorer, right-click your server, and then click Restart. If SQL Server Agent is running, it must also be restarted.
    5. Navigate to Start > All Programs > LANDesk > LANDesk Configure Services. Once opened edit the SQL connection information to reflect your new SQL server credentials. Once that is done, you'll want to reboot your core server so all your services start up with the new connection information.

     

    ss (2014-03-14 at 01.49.33).png

     

     

    Once this is done your core should now be pointing to your new database server and working as expected. At this point, you may want to consider detaching or deleting your old database from the old SQL Server, though this would be up to your discretion. If you're doing a side by side upgrade I would suggest that you keep a copy of this old database around for a while so you can work out any kinks in your upgrade process and have something to fall back to in case there are problems.