mibuso.com
Home› SQL General
Options

Error on NAV restore

ta5ta5 Member Posts: 1,164
edited 2012-01-17 in SQL General
Hi
We are testing a migration with a db containing about 50 companies. If restoring more than ca. 10 companies at a time (NAV internal restore, not sql restore) we get this error:

"Die folgenden SQL Server-Fehler sind beim Zugriff auf die Tabelle 'Object' aufgetreten:
701,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]There is insufficient system memory in resource pool 'default' to run this query."

Everything on SQL Server 2008R2, Windows Server 2008 R2, NAV 2009 R2.

Anybody seen this error message before?

Thanks in advance
Thomas

Answers

  • Options
    bbrownbbrown Member Posts: 3,268
    Are you by any chance using 32 bit SQL?
    There are no bugs - only undocumented features.
  • Options
    ta5ta5 Member Posts: 1,164
    Hi bbrown
    No, its 64 Bit. Thanx.
    Thomas
  • Options
    davmac1davmac1 Member Posts: 1,283
    Next question - how much RAM do you have dedicated to SQL Server?

    I thought they were going to fix the problem that caused restoring mmany companies to chew up memory in SQL Server.
    Maybe they did and got unfixed.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • Options
    ta5ta5 Member Posts: 1,164
    We have a virtual server with 4 GB.
    2 GB dedicated to SQL Server.

    Regards
    Thomas
  • Options
    ta5ta5 Member Posts: 1,164
    Latest news. We configured the sql server now with 3 GB, still same error. Now splitted the restore into 2 Parts (each about 20 companies), this worked.
    Regards
    Thomas
  • Options
    davmac1davmac1 Member Posts: 1,283
    Is RAM that expensive in Switzerland?
    Why not assign 8GB or or higher?
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • Options
    ta5ta5 Member Posts: 1,164
    No no, RAM is not that expensive 8) . But its on a virtual box and for some reason they only want to give 4 GB. Still strange, I thought if sql server is stalling on RAM it would get veeery slow, but I did not know that a runtime error could be thrown.

    Regards
    Thomas
  • Options
    bbrownbbrown Member Posts: 3,268
    You never say how large this DB is. But I take it to be good size with that many companies.
    There are no bugs - only undocumented features.
  • Options
    David_SingletonDavid_Singleton Member Posts: 5,479
    2 gig for 50 companies. That sounds very low. You should add more.
    David Singleton
  • Options
    ta5ta5 Member Posts: 1,164
    The DB is quite small, only 2.5 GB. As mentioned before, performance is absolute not the problem. The db is used for the accounting of all these small companies.
    I was just puzzled why SQL Server would throw an out of memory exeption...
    Thanks
    Thomas
  • Options
    davmac1davmac1 Member Posts: 1,283
    You are restoring objects and SQL Server table definitions and it commits when the process is finished. You create over 1000 tables for each company you restore - this is regardless of data size.
    If your version is prior to version 5, you create SIFT tables as well. The new versions, you create managed views - more SQL Server objects.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
Sign In or Register to comment.