Hi Hennie, One of your mayor problems could be that
you only use a limited number of inventory dimensions (maybe only the default
one). The reason for this is that some of Axaptas
central processes are joining the inventory dimension table when doing updates
(select inventtrans forupdate ... join inventdim …) – and this will result in wait-time
for all other processes requesting to perform updates on transactions with this
inventory dimension. Another thing is that on MS-SQL: “Writer
blocks reader” – meaning that another process can not read a record
which is locked for update by another process – before this process has
finished its update. This is only a problem when running MS-SQL server –
but there exists some workarounds which requires coding (eg.
Using the selectLocked() option when selection data). I would suggest that you have a
performance analysis performed on your Axapta installation – this to
identify the processes causing the locking/blocking. Regards, Karsten Wollesen Clausen Thy From: Hennie Potgieter
[mailto:[EMAIL PROTECTED] 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
Sharing the knowledge on Axapta.
Yahoo! Groups Links
|
Title: Message
- [Axapta-Knowledge-Village] Axapta performance Hennie Potgieter
- RE: [Axapta-Knowledge-Village] Axapta performance James Flavell
- RE: [Axapta-Knowledge-Village] Axapta performanc... Hennie Potgieter
- RE: [Axapta-Knowledge-Village] Axapta perfor... James Flavell
- [Axapta-Knowledge-Village] Re: Axapta performance RALorenz
- [Axapta-Knowledge-Village] Re: Axapta performance luisxbmo
- RE: [Axapta-Knowledge-Village] Axapta performance Karsten Wollesen
- RE: [Axapta-Knowledge-Village] Axapta performanc... Hennie Potgieter
- RE: [Axapta-Knowledge-Village] Axapta performance Matt Birtwistle
- RE: [Axapta-Knowledge-Village] Axapta performanc... James Flavell