Hi

As far as I know, MS SQL has something like a "lock escalation" procedure. This means that when (from Axapta), some records are locked, the MS SQL first makes a record lock.
If more records are to be locked, it makes a page lock.
And if even more records are to be locke, it makes a table lock.

I do not know if there's anything you can do against it from the SQL side, coz I'm not really an SQL specialist (the wisdom above was told to me by one).

In Axapta, however, you might consider activating the IMTS system. I think a description of it is available on the SP2 docs.

Best regards
Helmut

-----Urspr�ngliche Nachricht-----
Von: subhamit59 [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 13. September 2004 17:26
An: [EMAIL PROTECTED]
Betreff: [development-axapta] Exclusive table locking

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 Table when our users trying for invoicing (Attach Sales Tax) at a time.
This kills the user experience...

Plese help.




------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
--------------------------------------------------------------------~->


Yahoo! Groups Links







Yahoo! Groups Sponsor
ADVERTISEMENT
click here


Yahoo! Groups Links

Reply via email to