R
ryanbreakspear
Hi guys,
I've written an application which does an xsl transformation (into a
memory stream) to generate a load of sql insert statements. I then
loop through this, and execute the sql (into Access). (I'm using .Net
v1.1)
The transformation is quite slow, but I'm not too bothered about that
(I've read it'll be much faster in .Net V2.0). When the application is
doing the insert statements, it uses 100% of the cpu (as expected), and
inserts about 200 records/second. If I open Microsoft Access, it grabs
all the cpu time (as Access does), but when I close it, the system idle
process has all the CPU time rather than my C# app. Has anyone else
seen anything similar, is there anything I can do to grab all the
resource back for my application? After I've closed Access, my
application runs much, much slower.
I've looked at setting the priority of my process to "High" in c#, but
doing this manually in Task Manager doesn't seem to make any
difference.
Any ideas would be much appreciated.
Thanks in advance
Ryan
I've written an application which does an xsl transformation (into a
memory stream) to generate a load of sql insert statements. I then
loop through this, and execute the sql (into Access). (I'm using .Net
v1.1)
The transformation is quite slow, but I'm not too bothered about that
(I've read it'll be much faster in .Net V2.0). When the application is
doing the insert statements, it uses 100% of the cpu (as expected), and
inserts about 200 records/second. If I open Microsoft Access, it grabs
all the cpu time (as Access does), but when I close it, the system idle
process has all the CPU time rather than my C# app. Has anyone else
seen anything similar, is there anything I can do to grab all the
resource back for my application? After I've closed Access, my
application runs much, much slower.
I've looked at setting the priority of my process to "High" in c#, but
doing this manually in Task Manager doesn't seem to make any
difference.
Any ideas would be much appreciated.
Thanks in advance
Ryan