Regarding recordset operations:
Note that this only works if no code exist on the insert/update events methods on the table, otherwise it will fall back to the traditional 1 by 1 insertion/update.
However this can be bypassed by using the skipDataMethods() method -but careful now you must be 100% sure on what you're doing.
Alternatively, you could try using the recordInsertList, this is actually documented in \System Documentation\Classes\RecordInsertList
ttsCommit
Should be called after the last update,
Client/server:
Make sure that your code is running on the server, thus eliminating cross-tier calls.
Primary Index:
I assume you have a primary index!
Cluster Index:
When used, this is often your primary index.
If your primary key's values are consecutive the data is handled ok - however if the values assigned to the primary key are not consecutive every insert will cause the database to reorganize data for optimal fetch of the records afterwards.
If the problem persists, you should tell us a bit more about the environment.
Med venlig hilsen/Best regards
Jacob Hjelmer
thy:development
Søvej 13B
DK-3460 Birkerød
Tlf.: +45 96 170 470
Fax: +45 45 824 544
Mobil: +45 24 474 032
E-mail: [EMAIL PROTECTED]
www.thydevelopment.com <http://www.thydevelopment.com/>
www.x-masterclass.com <http://www.x-masterclass.com/> High-end education program for Axapta developers.
________________________________
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dilip N
Sent: 4. januar 2006 13:39
To: [email protected]
Subject: Re: [development-axapta] Performance Issue
Maverick:
Try using INSERT_RECORDSET / UPDATE_RECORDSET..This will speed up the operation.
Good luck
Regards,
Dilip
Maverick <[EMAIL PROTECTED]> wrote:
Hi All,
I have some code which is processing thousands of update on the table. This process is doing all the updates on one table. Updates consists of inserting new record and updation of a record.
The process consist of a loop, doing updation on a table on every record conditionally. And this is done several times. And table consists of million of records.
What are the ways to optimize the process. Please do tell me all the points to be taken care in the CODE,TABLE and in the SQL.
Like:
When should TTSCOMMIT be done. If it is done after every update it will take too much time. And if it is after thousands of update, it takes runtime memory.
What about Index, should it be primary OR cluster.
What properties of SQL Server should be set for better updation.
If you would like to put light on any other point, it willl be very helpful.
Thanks
Maverick
[Non-text portions of this message have been removed]
SPONSORED LINKS
Computer part Programming languages Microsoft axapta Support exchange
---------------------------------
YAHOO! GROUPS LINKS
Visit your group "development-axapta" on the web.
To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
---------------------------------
---------------------------------
Yahoo! DSL Something to write home about. Just $16.99/mo. or less
[Non-text portions of this message have been removed]
________________________________
YAHOO! GROUPS LINKS
* Visit your group "development-axapta <http://groups.yahoo.com/group/development-axapta> " on the web.
* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
* Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> .
________________________________
[Non-text portions of this message have been removed]
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
