|
Posted by Dan Guzman on 08/17/06 11:34
> It takes 4 minutes to insert 40 000 records on a SQL Server
This performance is exactly what I would expect when each insert is done in
an individual transaction and there is no write caching. A physical
transaction log write is required during COMMIT to guarantee that data are
permanently persisted and a disk can typically sustain only 150-200 I/Os per
second.
Server grade hardware usually has write-caching that greatly improves write
performance while ensuring persistence (e.g. controller cache battery
backup). However, you can probably improve performance greatly with your
current configuration by performing the inserts in a single transaction.
This ought allow you to achieve the kind of performance Daniel alluded do.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Volks" <patrick.simard@isac-inc.com> wrote in message
news:1155756964.614937.145000@h48g2000cwc.googlegroups.com...
> Hi,
>
> It takes 4 minutes to insert 40 000 records on a SQL Server and 40 sec
> on an other SQL Server. The slower run on windows 2000 terminal server
> and the faster on windows 2000. The slower The slower have 2 Go of
> ram, the faster 512 Mo!!!
>
> How to diagnostic what's going wrong on the slower server? I can't
> change the application who do the insertions.
>
Navigation:
[Reply to this message]
|