次の方法で共有

Task 6: Create the New Microsoft Dynamics NAV Database

  • [アーティクル]

This topic describes how to create a new Microsoft Dynamics NAV database.

To create the new database

  1. Make a copy of the current database.

  2. Close the Microsoft Dynamics NAV 2009 Classic client.

    Note

    When you close the Classic client after you delete objects, you might see errors regarding objects that no longer exist. You can ignore these messages, which appear because of references to deleted objects still in memory (in the CompanyClose procedure in Codeunit 1 Application Management). These messages will not appear again.

  3. Uninstall Microsoft Dynamics NAV 2009.

    Note

    It is possible to install Microsoft Dynamics NAV 2009 on a computer where Microsoft Dynamics NAV 2013 R2 is already installed. So if you have to open the old database using the Microsoft Dynamics NAV 2009 Classic client after you have installed Microsoft Dynamics NAV 2013 R2 on the same computer, you can do so. But for now you must uninstall Microsoft Dynamics NAV 2009. You have the option of reinstalling it later.

  4. Use the following list to verify that the user performing the upgrade has the necessary roles and permissions in SQL Server Management Studio:

    • Verify that the user has the db_datareader, db_datawriter, and db_ddladmin database roles for the database. For information about how to grant these roles, see Provisioning the Microsoft Dynamics NAV Server Account.

    • Verify that the user has the sysadmin Server Role for the Microsoft Dynamics NAV SQL Server instance. For information about how to assign this role, see Setting Database Owner and Security Administration Permissions.

    • Verify that the default schema for the user's account is dbo. Do this by selecting the user account under Security/Users for the database to open the database user dialog box. Choose the AssistEdit button for the default schema field and choose [dbo] as the default schema.

  5. Use Microsoft Dynamics NAV 2013 R2 Setup to install the Developer Option, which includes the Microsoft Dynamics NAV Windows client, the development environment, Microsoft Dynamics NAV Server, and SQL Server database components. For more information, see Developer Option.

    Important

    For Microsoft Dynamics NAV 2013 R2, you must install Microsoft Dynamics NAV Server on a 64-bit operating system. Microsoft Dynamics NAV also requires a 64-bit edition of SQL Server. If no usable edition of SQL Server is found on the target computer, Setup installs a 64-bit edition of SQL Server 2012 Express.

  6. For SQL Server 2008 and SQL Server 2008 R2 editions, verify that the compatibility level of the database is set to 100. For SQL Server 2012, set the compatibility level to 110.

    To do this, start Microsoft SQL Server Management Studio and connect to the SQL Server instance that the Microsoft Dynamics NAV database is attached to. Right-click the database and select Properties. In the Database Properties window, select the Options page, and then verify that the Compatibility Level is set correctly.

  7. Open the Microsoft Dynamics NAV Development Environment.

  8. Open the database that you copied in step 1. When you do this, you will be prompted to convert the database. The conversion performs the following:

    • Updates system tables.

    • Enables Unicode in the database objects.

    • Upgrades to the newest Windows collation. Utilizing SQL collations for the database is no longer supported in Microsoft Dynamics NAV 2013 R2. If your database has been using a SQL collation, or an out-of-date Windows collation, the development environment will offer to perform a collation upgrade alongside the Unicode upgrade. If you are not satisfied with the choice of collation, you can switch to the desired collation after the upgrade is completed. For more information, see How to: Alter Databases.

      The collation upgrade will set the default database collation and the column-level collation for all columns in tables, except for variant, to the chosen collation value. Variant columns will have the collation value stamped on each instance’s metadata.

    • Marks all objects in the database as "not compiled."

    This conversion can take a while, especially for larger databases. After the conversion, expand the size of the database to the size that you noted at the end of Task 4.

  9. Upload your Microsoft Dynamics NAV 2013 R2 Developer’s License to the Microsoft Dynamics NAV database.

  10. Configure Microsoft Dynamics NAV Server to connect to the new database.

    Start the Microsoft Dynamics NAV Server Administration tool and select the appropriate Microsoft Dynamics NAV Server instance in the left pane. Choose the Edit button at the bottom of the settings list in the center pane and update the Database Instance, Database Name, and Database Server options to point to the converted database. Choose the Save button when you are finished.

  11. Restart the Microsoft Dynamics NAV Server instance.

    In the left pane of the Microsoft Dynamics NAV Server Administration tool, select the local Microsoft Dynamics NAV computer. In the center pane, right-click the Microsoft Dynamics NAV Server instance, and then choose the Restart button.

See Also

Concepts

Configuring Microsoft Dynamics NAV Server
Microsoft Dynamics NAV Server Administration Tool