Hello, At the moment we are looking to Axapta. It seems that you have the choice between two databases being SQL and Oracle. Can anyone give me some experiences about what is the best database ? We are going to get about 250 concurrent users. Thanks in advance Adri Donkers
We are an US Based company providing solutions inAxapta. Could you please give us your contact details and we shall get in touch
Hi Adri, unless you’re already using Oracle and have internal Oracle expertise I would generally recommend SQL Server. In the earlier versions of Axapta (1.5, 2.0 and 2.1) there was a definate advantage by choosing Oracle. Since then the performance of the SQL Server with Axapta has improved greatly. I do believe that Oracle still might have the edge when it comes to ‘huge’ Axapta installations (1000+ concurrent users) and especially if it is a heavy manufacturing installation that generates loads on transactions. All in all I would go for SQL Server, but if you want to explore both Oracle and Axapta, have your Axapta partner do trial setups of both. I don’t think you will notice any differences - apart from the fact that Oracle often requires more maintenance and tuning to perform optimally. Regards, H. Jaeger Tectura UK
Hi I agree with Henrik, Oracle is too expensive. We have had a lot of problems with Oracle even if running a certified combination of Axapa+Oracle. Comparing to our MSSQL installations Oracle was very difficult to get running without deadlocks which jammed the whole server for minutes. We got very good advices from MBS - thx to Kim - and upgraded Oracle many steps to an ‘uncertified level’. But the indexes of the db must be calculated by a sript, becuse axapta uses those (f…ing) Function Based Indexes. Now it keeps calculating them 5 to 6 hours, and the customer has been live only for 4 months. What happens when there isn’t enough time to do daily indexing daily :-p
Hi I must also say that I have seen huge performance problems on a MS SQL 2000. There were about 200+ concurrent users on an AOS cluster plus additionally the system was loaded with cash machine data (you can say that would count for an additional 50-100 users). With that, we had to increase the SQL server to a Quad-XEON machine with about 4 (or 8) GB RAM. Then it was working okay.