Transaction Speed

RChurchill

Hi,

At the moment we are running 3.70 with a native database. When we run some very heavy batch processes we run them on the same server as the database connected locally and the speed and performance increases a lot.

We are going to migrate to sql with a later version of navision (probably NAV 2009). We have never run navision with sql before and would like to know if the above principal would still apply. Should (can) we run heavy processes on the same server as the sql database in order to speed things up.

Also the administrator is looking at setting up a clustered Microsoft SQL*Server back-end with shared application servers replicated in the two data centres. Any advice or experiences that can be shared on this set up would be invaluable.

Many thanks in advance

Rob

ara3n

RChurchill wrote:

Hi,

At the moment we are running 3.70 with a native database. When we run some very heavy batch processes we run them on the same server as the database connected locally and the speed and performance increases a lot.

We are going to migrate to sql with a later version of navision (probably NAV 2009). We have never run navision with sql before and would like to know if the above principal would still apply. Should (can) we run heavy processes on the same server as the sql database in order to speed things up.

yes.

Also the administrator is looking at setting up a clustered Microsoft SQL*Server back-end with shared application servers replicated in the two data centres. Any advice or experiences that can be shared on this set up would be invaluable.

use transaction log replacation