RE: Improving insertion performance by locking tables

2003-07-14 Thread Rudy Metzger
;line too long". Cheers /rudy -Original Message- From: Phil Bitis [mailto:[EMAIL PROTECTED] Sent: maandag 14 juli 2003 11:44 To: [EMAIL PROTECTED] Subject: Re: Improving insertion performance by locking tables Is there a limit to the number of records I can insert in a multiple-value insert?

Re: Improving insertion performance by locking tables

2003-07-14 Thread Phil Bitis
rts). Multi inserts are the way to go. By locking the table you actually would loose time. /rudy -Original Message- From: Phil Bitis [mailto:[EMAIL PROTECTED] Sent: zaterdag 12 juli 2003 19:00 To: [EMAIL PROTECTED] Subject: Improving insertion performance by locking tables Hello, We've got

RE: Improving insertion performance by locking tables

2003-07-14 Thread Rudy Metzger
ble you actually would loose time. /rudy -Original Message- From: Phil Bitis [mailto:[EMAIL PROTECTED] Sent: zaterdag 12 juli 2003 19:00 To: [EMAIL PROTECTED] Subject: Improving insertion performance by locking tables Hello, We've got an application which does many multiple-value in

Improving insertion performance by locking tables

2003-07-12 Thread Phil Bitis
Hello, We've got an application which does many multiple-value inserts to different tables. Is it worth locking a table before doing a multiple-value insert with say 50 records? If so, what is the number of records that makes it worthwhile? If not, is it worth locking a table before doing 2 seper