It's my experience that heavy data access can result in a very high load
on the database CPU. In some case you can help the situation a lot by
identifying the top-10 of time consuming queries - and ensuring that all
of these queries are optimized.
So my suggestion is that you use Axapta's built-in SQL trace feature to
identify the Top-10 of time consuming queries. This is done by running
the "Long queires"- trace with the Threshold set to for example 3000 (3
sec). This can be setup under Options/tools/SQL/Long queries and also
in the Axapta configuration.
The general problem with long running queries doing updates is that they
lock a lot of transactions and also holds these locks for a long time -
this is especially "painful" when running in a multi-user environment.
Best regards,
Karsten Wollesen Clausen
Thy Data Center Development A/S
http://development.thydatacenter.dk/
[Non-text portions of this message have been removed]
| Yahoo! Groups Sponsor | |
|
|
Yahoo! Groups Links
- To visit your group on the web, go to:
http://groups.yahoo.com/group/development-axapta/
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
