Basic SQL - How to create a new NAV database for restoring a NAV backup

  • 아티클

This post is part of "Overview of NAV-specific SQL features for application consultants". 

 

This post describes the steps needed to create a new NAV database from a NAV backup (.fbk) file. All the steps are done from a NAV client:

1)     Start a NAV client (finsql.exe), then go to File -> Database -> New. In Server Name, enter (local)  - assuming you have SQL Server on the same machine. Then click OK.

2)    You only have to enter a database name, and click OK. But if the database is used for test purposes, I would also recommend you change “Recovery Model” from Full to Simple (Options tab), and change “Security Model” from Enhanced to Standard (Advanced tab). Then click OK.

3)    Now you have a blank NAV database. All you have to do, is to restore your NAV backup (.fbk) file: Tools -> Restore.

4)    If you want to change the NAV license, then go to Tools -> License Information, and click Upload, and select the NAV license. This uploads the license to the SQL Server, and it will be stored there for the next time you start NAV.

 

 

Lars Lohndorf-Larsen

Microsoft Dynamics UK

Microsoft Customer Service and Support (CSS) EMEA

These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use.

Comments

  • Anonymous
    November 05, 2008
    PingBack from http://blogs.msdn.com/nav_developer/archive/2008/11/05/basic-sql-overview-of-nav-specific-sql-features-for-application-consultants.aspx

  • Anonymous
    November 10, 2008
    Hi Lars, I would be happy to hear from you examples on when you should use the Extended security model. My experience so far tells me that the standard is much better - but I also guess there most be a reason why Microsoft have made Extended the default security model.

  • Anonymous
    November 11, 2008
    Hi Erik, Good question. I would say: The options are "standard" and "Enhanced", not "good" and "bad" security. As with other MS security settings, NAV defaults to the enhanced setting. But unless you have a need for enhanced security, then consider if the extra admin (synch) is worth it. Functionality wise the two models do the same. And Standard model is the same that we had before version 4, so it is by no means unsecure. There is an updated chapter on security model in w1w1isql.pdf on the product CD for V5 SP1, listing more differences between the two models. But the simple answer is: Standard is simpler to manage, while Enhanced requires more admin. Hope this helps a little? Lars