RE: [Axapta-Knowledge-Village] Exclusive Table locking in SQL

[Preston A. Larimer]

Here are some notes I have, in addition to these the users should set the credit check on the other tab of the saleseditlines form to none when invoicing, doesn’t make sense to check credit limits when creating an invoice.   -Preston   Axapta 3.0 Locks Up During Sales Order Update If multiple sales orders are selected for update or the select feature is used during on the salesEditLinesForm the Sales order table can be blocked for a prolonged time causing multiple users to experience long delays in creating and updating sales orders. The salesFormLetterClass chooseLines method places the salesTable table and salesLine table in transaction state as it populates the parm table with the selected records. If a user is selecting a large amount of records or the selection criteria is complex this causes the long block on theses two tables and can block work with sales orders for every other user in the system. The block is possibly due to the credit check process which also wants to traverse the salesTable and salesLine tables while checking for open sales order totals during order creation and update. Fix: Modify salesFormLetter::chooseLines, comment out line 20 and line 53 in the unmodified sys layer code. Axapta 3.0 Locks Up During Credit Check During processes that perform credit checks in Axapta the salesTable and salesLine tables can be blocked causing excesive delays for users wanting to update sales order records. This is noticed in sales order update processes that use the salesFormLetter class and invoke credit checking during the update the checkSales method of the salesFormLetter class places multiple tables in a transaction state while it reads their data. This blocking issue is most severe if the client has invoiceing accounts with multiple associated customer accounts and a substantial amount of uninvoiced orders. Fix: Modify salesFormLetter::checkSales comment out line 6 and line 21 in the unmodified sys layer code       -----Original Message----- From: subhamit59 [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 10:21 AM To: [EMAIL PROTECTED] Subject: [Axapta-Knowledge-Village] Exclusive Table locking in SQL   Anyone knows how to get rid off exclusive table locking in SQL because our users cannot work due to X TAB locks. The system is heavily loaded with transactions on SQL2000 SP3a. The memory usage on SQL seems to stay at around 100% from the 3Gb. The SQL server has DUAL processors The SQL is about 13Gb in 3Months, with 1.6 Million inventTranses. We have X TAB locks mostly on inventSum, inventTrans, salesline, inventJournalTrans,InventdimId,SalesTable. Mostly on Sales when our users trying for invoicing (Attach Sales Tax) at a time. This kills the user experience... Plese help. Sharing the knowledge on Axapta. Sharing the knowledge on Axapta. Yahoo! Groups Sponsor ADVERTISEMENT 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.