Re: dts quick to access 97 but slow to access 2003
- From: "Andrew Brill" <dragon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 29 Sep 2005 15:54:18 +0100
I have noticed the network usage during this is excessive.
It's using 40% of the client and the file servers 100mbs connection network.
By my calculation, in the hour it runs for it could transfer 18Gb in that
time and it's only creating a 50Mb database.
The SQL Server itself is using a fraction of a percent - although it's page
file usage is 1gb and it only has 1gb of ram.
The CPU occupancy is nothing on the sql server, 30% on the file server and
60% on the client. That's a fair amount of processing over an hour too.
"Andrew Brill" <dragon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:O1gwcDPxFHA.3860@xxxxxxxxxxxxxxxxxxxxxxx
> "Allan Mitchell" <allan@xxxxxxxxxxxxxxxxxx> wrote in message
> news:OIG$ZcOxFHA.2932@xxxxxxxxxxxxxxxxxxxxxxx
>> Jet driver differences?
>>
>
> Is there anything I can do about these differences?
> I note that it's quick if I use ODBC to connect to the database rather
> than setting Microsoft Access (with access 97 icon) as the Data Source.
> I'm not too familiar with ODBC but it looks like this unfortunately
> requires me to setup a DSN for every database file on every client
> machine.
>
.
- Follow-Ups:
- Re: dts quick to access 97 but slow to access 2003
- From: Andrew Brill
- Re: dts quick to access 97 but slow to access 2003
- References:
- dts quick to access 97 but slow to access 2003
- From: Andrew Brill
- Re: dts quick to access 97 but slow to access 2003
- From: Allan Mitchell
- Re: dts quick to access 97 but slow to access 2003
- From: Andrew Brill
- dts quick to access 97 but slow to access 2003
- Prev by Date: DTS, msdb and the case of the missing statistics
- Next by Date: Re: dts quick to access 97 but slow to access 2003
- Previous by thread: Re: dts quick to access 97 but slow to access 2003
- Next by thread: Re: dts quick to access 97 but slow to access 2003
- Index(es):
Relevant Pages
|
Loading