mibuso.com

Hello All,

I am trying to migrate from FDB to SQL Server. I took a backup of the live database and did the followint:

1) Restored the FBK as FDB on a test environment
2) Ran a full database test
3) Used migrate.fob from Upgrade toolkit and made all necessary corrections to make the DB SQL Ready
4) Took a fresh fbk of the database
5) Created a blank SQL database
6) Tried restoring the "SQL Readied" fbk, Custome Restoration, Only the "Data Common to All Companies" and "Application Objects" first

I am getting the attached error.

"There is not enough memory to execute this function.

If you work in a single-user installation, you can try reducing the value of 'cache' program property."

Tried this on the server machine where I have SQL Express Edition, also on a local machine with SQL Express Edition (The FDB size is 2.5 GB and the FBK is around 700 MB)

Have anyone encountered and countered this error ever?

Please help

Najja

***NOT SURE ABOUT THIS***
I think Sql express does not support Databases bigger than 2GB
***NOT SURE ABOUT THIS***

http://msdn.microsoft.com/en-us/library ... 90%29.aspx

limit for 2005/2008 is 4GB, 2GB were for 2000 if I am not wrong...

The limit is 4 GB in SQL express edition 2005+. The reason why I mentioned the DB size was precisely not to divert the discussion to the limitation of the Express Edition.

An update from my side: Tried restoring the DB to SQL Standard Edition, result is the same Getting the same error.

Please help !!

Najja

1) Are you using latest client version?
2) How much memory you have? (I assume that enough)
3) What about free disc space? Mainly where the temp folder is placed...

Thanks kine for the reply:

1) I am using NAV 2009 (not SP1 as the DB is for ver 6.0)
2) I have 4 gig RAM on the Box (not running any other major applications)
3) More than 20 gig available on C and plenty on the data drive

Any help appreciated.

Najja

There was a bug back in version 4 where this error would occur if the backup contained a large value in a BLOB field. Not that MS would re-introduce a previously corrected bug.

Any solutions to this? Having the same problem with NAV 2009, SQL 2008 and I'm only restoring common data and application objects. Have 80GB available space 8GB ram

There was a problem restoring a large number of companies using the 32 bit version of SQL Server.
This was finally fixed - don't know which version. They did come up with a workaround before they fixed it.
Are you using 64 bit SQL Server?

Yeah, it is the 64bit version which I'm running om my 64bit win7 machine.

If you are using Win7, it means you are using desktop system (or notebook). These systems are not optimized for high performance for server systems. I expect that you do not have dedicated discs for different parts of the system etc. Do not expect some super performance....

Found the solution!

I don't know if this is a performance issue but I noticed that everytime it gets "Out of memory.." it was restoring the codeunits for migrating to SQL (codunits in migrate.fob for SQL migration). It seems that restoring one of these codeunits would eat up to 2GB memory and then I would get this message.

My solution was to remove all the objects that comes from migrate.fob and the objects from the upgrade toolkits (upgrade from 3.01 to 2009). After that the restore went smoothly

Two years later I have the same problem (another db). Fortunately I found my own post and could implement the solution AGAIN

I had the same problem. Then, before I created the backup of the fdb I deleted the very big "FieldCheck" object (Codeunit 104015) and everything worked fine.