Performance comparison on Update vs. UpdateBatch - record by record
From: Jiho Han (jhan_at_infinityinfo.com)
Date: 10/28/04
- Next message: Apple: "Re: Indexing a Table"
- Previous message: JasonAu: "Re: access via ado slow"
- Next in thread: Anushi \(Grapecity\): "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Anushi \(Grapecity\): "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Val Mazur: "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Michael D. Long: "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 28 Oct 2004 06:59:43 -0700
I was wondering if there are any significant performance difference between using Update vs. UpdateBatch (adLockOptimistic vs. adLockBatchOptimistic).
I don't mean to batch up changes and call UpdateBatch. I would be calling UpdateBatch on every record change basically.
I know I could simply use Update in this case but that's not the point.
Thanks much.
Jiho
- Next message: Apple: "Re: Indexing a Table"
- Previous message: JasonAu: "Re: access via ado slow"
- Next in thread: Anushi \(Grapecity\): "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Anushi \(Grapecity\): "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Val Mazur: "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Reply: Michael D. Long: "Re: Performance comparison on Update vs. UpdateBatch - record by record"
- Messages sorted by: [ date ] [ thread ]