Skip to main content

Copy Navision Data Between Databases using SQL Server


Hi all,

Microsoft SQL Server has an import and export wizard that assists you in copying Navision data from one database to another. This import and export wizard is available in any version of SQL Server, and it lets you copy tables, data, functions and other database objects. This is beneficial when you want to move your Navision data to a faster server for better querying performance.



Steps to Perform -

1. Click the Windows "Start" button and select "All Programs." Click "SQL Server" and select "SQL Server Management Studio" to open the database configuration software.

2. Right-click the database server name and select "All Tasks." Click "Export Data" to start the wizard. Click "Next" on the first window to move to the configuration setup.

3. Click "Next" in the "Data Source" window. The wizard automatically places the current SQL Server information in the text boxes for you. In the next window, type the name of the target database where you want to send the Navision information. Click "Next."

4. Select the first option labeled "Table(s) and view(s) from the source database." Click "Next." The next window shows all the available Navision tables. Click the "Select All" option to choose all of the tables and click "Next."

5. Click "Next" until you reach the final window. Click "Finish" to start copying the data. It takes several minutes to copy all of the data, depending on the size of your tables.

Thanks & Regards
Saurav Dhyani
http://saurav-nav.blogspot.in/

Comments

  1. Hi,
    About an error that you have
    "The database compatibility level 90 is too low for this version of the Microsoft Dynamics NAV Development Environment.Change the compatibility level to 100 before reopening the database."

    I think this is a SQL server Requirement not NAV problem, if your compability level is 90 you are using a database created in SQL 2005. if you already are working with SQL 2008 you can change the compability level of a database under the database options

    ReplyDelete

Post a Comment

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.