Slowed when moved

[rcollman]

Client moved a Pervasive database to a RedHat sever from a workstation. In Access I have a routine that imports 6 files and a button on the switchboard that triggers the process. Before the move, when Access, its databases and the pervasive databases were all on the workstation, it took less than 5 minutes. I had to repoint things in my procedure. Now the process takes more than 30.

I think my problem is that I am importing 6 files seperately, rather than a group. When the network was not involved this was not an issue. It sounds (how low tec is that) like it is opening up the DD 6 times.

Here is an example of how one file WORKORD in brought in. This repeated for each of the other 5 files.

DoCmd.TransferDatabase acImport, "ODBC", "ODBC;DSN=LittleRedCI;ServerName=10.10.10.100.1583;ServerDSN=LittleRedEI;ArrayFetchOn=1;ArrayBufferSize=8;TransportHint=TCP:SPX;;TABLE=workord", acTable, "WORKORD", "WORKORD1", False
DoCmd.RunSQL "delete * from workord ;", 0
DoCmd.RunSQL "insert into workord select * from workord1", 0
DoCmd.DeleteObject acTable, "workord1"

Of course the above comes from my office machine (Access and its database on my Win98 workstation, Pervasive database on my little NT Server.

Thanks
Chris

 

[rcollman]

Our hero discovered the cause. In ODBC (Control Panel > ODBC32) There is a tab called Tracing, with two confusing buttons in Win98. Make sure the button is toggled to read "Start Tracing Now", so that it is turned off. See the default SQL.log file? That is where all the activity is/was taking place.

My client's file was 350 megs, because they update their files 3 and 4 times a day. My home office machine suffered the same fate. My bald head does not remember seeing, much less turning on this feature.

Chris
Chris