Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Restoring the Microsoft Dynamics SL databases for troubleshooting

Restoring the Microsoft Dynamics SL databases for troubleshooting

View products that this article applies to.

INTRODUCTION

Technical Support for Microsoft Dynamics SL may request that you test in a copy of your production database for troubleshooting purposes. This article describes restoring the Microsoft Dynamics SL databases for troubleshooting.

Note The Microsoft Dynamics SL licensing policy enables you to set up a test installation of Microsoft Dynamics SL. The test installation resembles the production environment. This installation includes the program files and the databases. Setting up a test environment requires the same storage space requirements as the production environment. The number of users in the test installation plus the number of users in the live installation cannot exceed the total number of licensed users who are permitted in the license agreement.

↑ Back to the top

More Information

To restore the Microsoft Dynamics databases for troubleshooting, follow these steps:
  1. Verify that the current installation and customizations are functioning correctly.
  2. Make all users exit from Microsoft Dynamics SL.
  3. Back up the Microsoft Dynamics SL system and application databases.


    For more information about how to back up SQL databases, click the following article number to view the article in the Microsoft Knowledge Base:

    867941 Creating a backup of the Microsoft Dynamics SL application database and system database by using Microsoft SQL Server 2008, Microsoft SQL Server 2005, or Microsoft SQL Server 2000

  4. Restore the databases, depending on the version of Microsoft SQL Server that you are running.

    Microsoft SQL Server 2005 and Microsoft SQL Server 2008
    1. Log in to SQL Server Management Studio.
    2. In the Object Explorer pane, expand the instance of SQL Server that hosts the Microsoft Dynamics SL databases.
    3. Right-click Databases, and then click Restore Database.
    4. In the To database box, type the new name of the database. For example, if you are restoring the system database for testing, you can type a name such as TestSystem.
    5. In the Source for restore area, click From device, and then click Browse.
    6. Click Add.
    7. In the Locate Backup File dialog box, browse to the location of your backup (.bak) file.
    8. Select the correct backup file, and then click OK.
    9. Click OK in the Specify Backup dialog box.
    10. In the Select the backup sets to restore section, click to select the Restore check box for the appropriate backup set.
    11. In the Select a page pane, click Options.
    12. In the Restore As box, confirm the location of the database files, and then click OK.
    13. Repeat steps 3 through 8 for each Microsoft Dynamics SL database that you want to restore.
    14. In the domain table in the Microsoft Dynamics SL system database, update the application database name. To do this, follow these steps:

      1. Click New Query.
      2. In the Available Databases list, select the Microsoft Dynamics SL system database, and then run the following statements:
        UPDATE COMPANY SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY' 
        UPDATE DOMAIN SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY'
        Note Replace XXXXXX with the new name of the application database, and replace YYYYYY with the old database name.
    15. Repeat step j for each application database that is associated with the Microsoft Dynamics SL system database.
    16. Update the database views. To do this, follow these steps:
      1. Click Start, click All Programs, click Microsoft Dynamics SL (Solomon), and then click Database Maintenance.
      2. Connect to the instance of SQL Server that is hosting the Microsoft Dynamics SL databases.
      3. In the System Database Name list, click the restored Microsoft Dynamics SL system database.
      4. Under Databases, click the restored Microsoft Dynamics SL application database.
      5. Click Update Views.
      6. At the bottom of the Database Maintenance (98.290.00) window, confirm that the progress bar has finished.
      7. If you are running Microsoft Dynamics SL 2011, click Synchronize All Ownership and Security in the Update Scenarios box.
      8. At the bottom of the Database Mainteance (98.290.00) window, confirm that the progress bar has finished.
      9. Click Close.
      10. Log on to Microsoft Dynamics SL by using the appropriate SQL Server name and the appropriate Microsoft Dynamics SL system database name.
    17. If you use the Windows Authentication security model, drop and then re-create the triggers on the Microsoft Dynamics SL system database. For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

      942095 Error message in any of various screens in Microsoft Dynamics SL: "SQL Server Message 10215 - Invalid object name"

    Microsoft SQL Server 2000
    1. Click Start, click Microsoft SQL Server, and then click Microsoft SQL Enterprise Manager.
    2. Expand Microsoft SQL Server, expand SQL Server Group, and then expand the instance of SQL Server that is hosting the Microsoft Dynamics SL databases.
    3. Right-click Databases, click All Tasks, and then click Restore Database.
    4. In the Restore database as box, type the new name of the database. For example, if you are restoring the Microsoft Dynamics SL system database for testing, you can type a name such as TestSystem.
    5. Under Restore, click From Device.
    6. Click Select Devices, and then click Add.
    7. Under File Name, click Browse, and then locate the database backup files.
    8. In the Backup Device Location dialog box, click OK.
    9. In the Choose Restore Destination dialog box, click OK.
    10. In the Choose Restore Devices dialog box, click OK.
    11. Click the Options tab.
    12. In the Restore Database Files as section, confirm the location of the database files, and then click OK.
    13. Repeat steps c through l for each application database that is associated with the Microsoft Dynamics SL system database.

    14. In the domain table in the Microsoft Dynamics SL system database, update the application database name. To do this, follow these steps:
      1. Click Start, click Microsoft SQL Server, click Query Analyzer, and then connect to the server that hosts the Microsoft Dynamics SL databases.
      2. In the Available Databases list, click to select the Microsoft Dynamics SL system database, and then run the following statements:
        UPDATE COMPANY SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY'
        UPDATE DOMAIN SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY'
        Note Replace XXXXXX with the new name of the application database, and replace YYYYYY with the old database name.
    15. Update the database views. To do this, follow these steps:
      1. Click Start, click All Programs, click Microsoft Dynamics SL (Solomon), and then click Database Maintenance.
      2. Connect to the instance of SQL Server that is hosting the Microsoft Dynamics SL databases.
      3. In the System Database Name list, click the restored Microsoft Dynamics SL system database.
      4. Under Databases, click the restored Microsoft Dynamics SL application database.
      5. Click Update Views.
      6. At the bottom of the Database Maintenance (98.290.00) window, confirm that the progress bar has finished.
      7. Click Close.
      8. Log on to Microsoft Dynamics SL by using the appropriate SQL Server name and the appropriate Microsoft Dynamics SL system database name.

↑ Back to the top

Keywords: kbfreshness2007, kbmbsenvironment, kbexpertiseinter, kbmbssqlserver, kbmbsinstallation, kbmbspartner, kbmbsmigrate, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 847681
Revision : 1
Created on : 1/7/2017
Published on : 6/6/2014
Exists online : False
Views : 508