The two main things I know can affect blocking are hardware and code.
I have experienced major blocking as a result of hardware. I understand the technical concept involved but I do not have all the details at hand.
You can use one server as the application and database server but this may not be ideal for your situation. The best configuration for top performance is at least one database server with a SAN unit for the data and an application server that may also be the object server if you are going 3-Tier. You may optionally use a different server for the object server. One object server should be adequate for up to one hundred users. Over that you may use two in load balancing mode.
Now blocking can be a result of the existence of a bottle neck with your hardware. The client in a 2-tier configuration and the object server in a 3-tier configuration constantly make requests to your database sever that include reading and writing of data. The communication link between the client/object server in such a situation needs to be high speed (I believe fiber may be the best medium). In addition to this the internal speed of the disks (you also have fiber disks) it also important. When requests are made to the database server the disks need to be able to process the requests as fast as possible otherwise one request may be waiting on another to be completed which results in blocking. Several of this may occur that lead to severe blocking.
The storage unit for the database should also be a combination of RAID 10 and RAID 15. RAID 10 is just striping while RAID 15 is a mirror of a RAID 10. Since the data files are very important you should but then on the RAID 15 and since the temp database and log files are not so critical you should put them on RAID 10. This will speed up the read/write process for the database and thus reduce blocking. RAID 5 saves you space but it is not ideal for read/write intensive operations since the process involves parity calculation.
The technology of the quad processor is advanced and can help in a big way. I do not know the details about this but I know it works.
If the specification of the application sever is not good enough this can also lead to blocking. I have personal experience where the database server was upgraded and the blocking was still the same. After upgrading the application server there was a major difference.
You must always have enough memory in your servers to ensure that there is not much caching. When you have over 3G of memory you need to enable windows to use it. You also need to enable Microsoft SQL to use over 3G (if you are using MSSQL).
The last thing is coding. You should ensure that transactions in the application are short. This means ensuring that you use tts.begin and tts.commit or tts.rollback in very short blocks of code where it is necessary. Otherwise tables/records may be locked in a waiting transaction that results in major blocking.
Hope this will be of some help to you.
Varden Morris
J. Wray & Nephew Ltd. - Group I.S.
Phone: (876) - 923 - 6141 Ext. 2226
Fax: (876) - 923 - 5372
Cell: (876) - 3833566
Email: [EMAIL PROTECTED]
SAS <[EMAIL PROTECTED]> wrote:
Dear all,
Do you have any experience how to minimize blocking on axapta ?
would you mind sahring your experience,
thx
sas
Sharing the knowledge on Axapta.
Celebrate Yahoo!'s 10th Birthday!
Yahoo! Netrospective: 100 Moments of the Web
Sharing the knowledge on Axapta.
| Yahoo! Groups Sponsor | |
|
|
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 the Yahoo! Terms of Service.
