This sounds really weird and I don't have an explanation for this:
I'm running an import program, written in VB, reading the same textfile over
and over again and writing the information in several tables (master with
many details). I want to write this way some 100.000.000 records to test
performance.
The program runs steady and for some days, writing between 60 en 80 record
per second in the mastertable. I check this with a simple query, the field
TrKey is increased by one and clustered indexed. I wait 3 seconds and print
the number of records written:
waitfor delay '00:00:03' -- wait 3 seconds
In the taskmanager I see SQL is using avg 17% CPU time, the import avg 15%.
Sometimes I noticed then the import writes around 150 records per second,
and be accident I found out that Windows Media player was the trigger (as
programmers we need some music at night, not?).
When I played a MP3 file with the Windows Media Player I noticed that around
150 per second are written per second.
When I check the taskmanager SQL takes around 45% and the import program
around 35% cpu time. Media player jumps between 0 and 2%.
When I stop playing the MP3 file or when the file is finished, I'm still
doing a 150 records per second.
When I terminate Media player immediately the number of records per seconds
drops between 60 and 80, and the cpu time of SQL and my application drops to
the old values again.
When I open a new MP3 file immediately the import process boosts.
Test configuration:
Pentium 2,8 with 512 MB
2xSATA 120Gb harddrives
Windows 2000 Proffesional SP3
MSSQL 2000 developer edition SP3 (from MSDN Subscriptions)
VB6 SP5
Configuration: Boost SQL Server priority switched on, other default
Someone has an explanation for this?
Rene