Donnerstag, November 24, 2005

Some facts about AOS clusters

For your information:

  • When you have a SQL cluster for failover and the actual failover happens, the AOS will lose the connection to the SQL server and you have to restart the AOS service.

  • When you have an AOS cluster and you set it to start "On demand", it will not work. If the AOS instances are not running they will never start when clients try to connect. Sad but true. Maybe this will change when we get the new Dynamics Ax 4.0.

Mittwoch, November 23, 2005

Where Breakpoints are stored for Axapta

If you ever wondered where Axapta stores the breakpoints, here is the answer:
breakpoints are stored in the registry under the key

HKEY_CURRENT_USER\Software\Navision\Axapta\3.0

Here's a screenshot:

Mittwoch, November 16, 2005

AOS Cluster on one server

Although the time might be near that we do not see the AOS clusters as they are now anymore(4.0 is coming!), here are a few words about clustering AOS in Axapta 3.0:

Normally, you use quite a good server for the AOS, let's say a dual Xeon with 3Ghz. That is, of course, way too much to ever be used by the AOS. So, what can you do ?
--> Just make a second AOS instance on the same machine! Put both instances into the same AOS cluster et voila!

Why does that make sense, you might ask. Well, one AOS instance (which means one ax32serv.exe) can only address 2GB of memory. That will be reached sooner than you think! Starting at around 150-180 users you will get dangerously near the 2GB. If you put 2 AOS instances on the machine, both of them can take about 150 users, that makes 300 users total.

If you have more users, you must add a second server (which you already have, of course).

Donnerstag, November 03, 2005

SQL Server 2005 released!

The SQL Server 2005 is already available for download. If you have an MSDN subscription, you will find all the versions there (Developer, Enterprise, Standard, Workgroup).