Kriki’s Dynamics NAV blog

Who is still on native DB? You really should think of migrating to SQL Server.

I still find some customers that are still on native DB. Some of them have problems with performance but mostly because the database is quite old and keeps growing. When they started, they maybe had 100 or 200MB of memory and in rare moments I even notice that the COMMITCACHE is no.

The best is to augment the DB Cache and set the COMMITCACHE to Yes.

How to do that? Well you can re-install the DB-service but I prefer to go into the registry and fix it there. Of course that can be very dangerous if you don’t know what you are doing (Trust me. I know what I am doing. (http://en.wikipedia.org/wiki/Sledge_Hammer! ).

First stop the service.

Start the registry editor (regedit.exe)

In the registry editor, search for the path+name of the db-file (the first file if you have more files), the path+name of server.exe, the name of the service. With all of those you will find the right entry (it is in HKEY_LOCAL_MACHINE=>SYSTEM=>Services.

You will find something like this (I didn’t copy the values column):

Here you can change the settings.

CACHE: the size in MB of the cache.

COMMITCACHE is 0 (=false) or (1=true)

Of course you can also change the other value, but I never tried that.

After you changed the value, just restart the DB service. It will have the new values (of course they must be legal values).

Filed under: Dynamics, NAV, NAVISION, NAVISION-DB, PERFORMANCE