Yes I did commit out the credit check long ago, because it
was taking forever on some orders.
I am also very familiar with Clustered Indexes, I just not
to sure how to actually create one through the AOT and Axapta.
Thanks!
-Brandon From: Axapta-Knowledge-Village@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Hennie Potgieter Sent: Wednesday, December 14, 2005 5:57 AM To: Axapta-Knowledge-Village@yahoogroups.com Subject: RE: [Axapta-Knowledge-Village] Peformance Issues Hi, Have a look at http://www.sql-server-performance.com/gv_clustered_indexes.asp As you can see,
clustered indexes are an absolute necessity (unless maybe for tables with LOTS
of update statements and few inserts/deletes). I also assume you are
not doing credit limit checking as part of the posting of a sales order
because this is known to be slow. Hennie ____________________________________________________________________________ From:
Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon George Thanks! My next step is
to use the code profiler. The thing that is strange, is that just last week it
was performing fine, and there have been Zero code changes to the code in the
area that is starting to perform slower - which is pretty much all
SalesFormLetter classes / processes (The entire Sales Life Cycle slowed down the
past two days). Anyway I will continue
to see what I can find out and keep everyone posted. I know that we will be able
to figure this out, I was just trying to get some fresh minds giving me some
fresh ideas. Thanks! - From:
Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Hennie Potgieter Hi
Brandon, We also had major
performance problems on our Axapta v3sp2 installation. Our biggest problem
area was Sales Ledger / Account Receivable. We definitely found that
adding clustered indexes to a number of the most heavily used tables improved
performance by quite a lot. Troubleshooting Axapta
performance unfortunately is quite a tedious process and you will have to
identify the key processes that are slow and need to be improved. While
troubleshooting a process a few weeks ago, I found the Code Profiler to be quite
valuable since you can see exactly
where the problem lies and then either make a code or an index change. I
found the SQL Index tuning wizard to be not that valuable since it does not
pinpoint the exact problem in the way that the code profiler
does. Good
luck, Hennie ____________________________________________________________________________ From:
Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon George I have been
researching, and done as much as I can with indexes / indices. I have added some
to a couple of Axapta Tables, that according to SQL Index Tuning Wizard should
improve overall performance by 18%. This will be some what of a boost, but not
quite the at least 25% I was hoping for. Also I have un-checked the initialize
for unicode' in the Configuration. I did, come across this
is a forum post: -AOS=hostIPaddress:port The user said that they
added as part of the command line parameters? I am wondering what does this do?
Anyway I am hoping that
someone can give me some more feedback as to what I can do to help improve
things. I have re-indexed everything, synchronized everything, etc. etc.
- From:
Axapta-Knowledge-Village@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Brandon George Hello
All, I was wondering
if anyone has ever came across using the Clustered Index and Primary Index
property fields of an Axapta table? Do setting these help performance at
all? We this week just
started having issues with performance and Axapta. I have been running
performance analyzer on SQL server and it seems as though the page life
expectancy has dropped from an avg. values in secs. of 5200 down to 1650. This
is the only real indication of the problem we are seeing. All the rest of the
SQL related performance items are doing just about the same. The page life
expectancy counter tells you, on average, how long data pages are staying in the
buffer. The higher the number the better. Dropping number here means more memory
is having to be used, and accessed more frequently.
Anyway I am puzzled,
and I am trying to find out the best way to address this, as the memory in our
SQL server is more than enough. I was wondering if anyone has any suggestions,
as my eye's are getting tired from looking at the same data and not coming up
with anything new.... thanks in
advance.... - Sharing the knowledge on Axapta. YAHOO! GROUPS LINKS
|
- RE: [Axapta-Knowledge-Village] Peformance Issues Brandon George
- RE: [Axapta-Knowledge-Village] Peformance Issues Varden Morris