Hennie, I agree with the suggestion made by one of the previous posters ... you need to check your SQL server. Here's what's NOT wrong 1. Your AOS's are not overtaxed, 2. Your SQL processors are not overtaxed 3. I assume your clients are not overtaxed This leaves 2 possibilities 1. The network connection between your AOS's and the SQL server is a bottleneck (I doubt this is the case, though) or 2. Your SQL server disk drives are the causing the slowdowns If the problem is #2, there are a few ways to remedy the situation: 1. Have your SQL admin check to make sure you have all the indexes you need for the types of jobs you're running. 2. Add more memory to the SQL server so that more of the database can be stored there. This will allow queries to be run completely from memory, which is 100's of times faster than physical disks. You will have to upgrade to the enterprise edition of SQL server, though. I think the standard edition is limited to using 2GB of memory. 3. If you have any other databases on the same server, like a testing / training environment, move them to another server. They may take up memory even when not in use. 4. Upgrade the disks in the server to a faster model, if possible. One last question Are you using the inventory multi-transaction option? (Admin ==> Setup ==> System) RAL --- In [EMAIL PROTECTED], "Hennie Potgieter" <[EMAIL PROTECTED]> wrote: > Hi, > > I want to rant about Axapta and if anyone wants to listen me out and > give any advise it would be appreciated..... > > Some Background: > We are a company in the courier and freight forwarding business and are > using Axapta mainly for financials (AR, AP, GL). We do not have > warehouses, BOM's, costing models etc. Our few (about 15) services that > we offer has been captured as service items in the Inventory module, but > other than this, we do not use inventory at all. Because Axapta is more > geared towards manufacturing, we had to customize quite a few components > to suit the services industry we're in. > > 1. We have major performance problems on Axapta - especially around > month end when the volumes of transactions reach a peak. > > 2. We are creating and posting around 25000 sales order per day with an > average of 5 lines per sales order. The performance of the posting is > not acceptable. We also get lots of database locks from this posting > process that sometimes takes minutes to resolve. We are running 3 AOS's > on the application server (dual 3GHz Intel box; 4GB RAM) and a SQL > Server DB on another hyper threaded 3GHz dual processor box with 4GB > memory. What is your volumes like? Is ours exceptionally big or not > really? Our AOS server is not straining. Our DB server sometimes hits > a bottleneck on disk I/O. > > 3. Because of our volumes, our database grows at an alarming rate. We > are 8 months into Axapta now, and our database size is around 54GB, and > growing at about 4 to 5 GB / month. If we need to keep like 5 years' > financial data I do not want to do the calcs. How big are your > databases and how do you manage the size? Has anyone developed some > purging/archiving solution yet or are we holding our breath for > Microsoft to come up with one in the next release? > > 4. We are getting serious database locks on SQL Server when running big > tasks simultaneously. What isolation level (allow dirty reads, read > committed, serializable etc.) does Axapta use for its transaction > processing and do I have any control over this? It sometimes seems as > if Axapta prefers locking on a table level rather than on a row level > and if these locks are exclusive, everyone waits! > > 5. Do you allow reporting off your main database, or do you have a > replicated / snapshot'ed database for reporting? Our performance > problems get 10 times worse when a user kicks off a biggish report. > Also Axapta was sold to us with the promise of users doing self- help > reporting, which seemed nice back then. But if a user filters / sorts > on a column that is not indexed on a table with 2.5 million rows it > brings the DB server to it's knees. Also if the user accidentally > klicks on the column heading on a form that displays a couple thousand > rows and the DB tries to sort the grid, it kills the performance. > > That was my 2 cents....... > > Any tips/hints appreciated! > > Hennie ------------------------ Yahoo! Groups Sponsor --------------------~--> $9.95 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/kGEolB/TM --------------------------------------------------------------------~-> Sharing the knowledge on Axapta. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/Axapta-Knowledge-Village/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
