When moving from the "native Navision" database to use SQL Server the way is to create a Navision backup and restore this into SQL Server.
But if you are restoring a very large Navision backup then it will be something that will take a very long time, even for a strong SQL Server. When Navision handles such a "native" restore it is doing it as one
huge transaction, thus causing super-load on the SQL Server. For each
company the table-objects have to be created, and their related indexes
and SIFT/VSIFT structures.
This all is causing tremendous write transactions, so also a
powerful disk-subsystem is essential. RAID5 is actually an absolute NO
GO for databases, especially for the Transaction Log file.
To reduce the "single impact" on the SQL Server, you could also proceed like this:
Preparation: SQL Database: "Recovery Model" SIMPLE. The "Security Model" should be "Standard" (anyway).
Also you should be running the Navision client directly on the SQL Server while doing this. You can remove it again after the restore.
Forums » Navision Forums / Microsoft Dynamics NAV Forums » Dynamics NAV / Navision - Microsoft SQL Server Forum » Performance issues with restore on SQL Server 2005 (Jörg Stryk)