Slow opening of databases under Windows 2000 Server

[redstag]

My multi user application written in Foxpro 2.6 for DOS operates correctly on a Windows 2000 server, however, the databases take ages to open relative to a Novell file server - Any ideas ?

Many thanks

 

[davidtoranzo]

Redstag,

Most probably it has to be with the file transfer protocols settings, but you may need to purge the volumes on the server to restore proper performance.

You can see if you have a heavy amount of disk requests in MONITOR | General Information | Current disk requests. Compare to a server not seeing performance issues to baseline.

To determine if you need to purge the volumes look in MONITOR | Volumes | Tab to the information for the volume. Then Take the Total Blocks and divide by the number of Free Blocks. This will give the percent of free space available. If that is below 10% at a bare minimum you need to purge the volume. The Freeable blocks in Salvage System will give you blocks available from performing a purge.

You can load TOOLBOX then perform the following to purge the volumes:

PURGE <VOL>: -A

Let us know if this helped!

David.

 

[redstag]

Thanks for responding.

I think that I have confused the issue.
The problem is with the Windows 2000 Server.
The databases open at a normal speed for the first user on the network. For subsequent users, the databases open very slowly.

Any ideas ?

 

[Guest_imported]

This is a known problem with W2K. Many of my clients have also complained about it. There is no known solution, as of yet, but I'm sure someone will eventually come up with something... I have heard some rumors that VFP6/7 is slow on W2K under same conditions, as well.

 

[SkyHawkTech]

just a thought.. why would you run a fox pro app on the server anyway?.. keep the executables on the locals and just store &quot;map to&quot; the data on the server.. w2k servers need hugh amounts of ram just to run by itself.. let alone a ntvdm process...


Rick Leske
IT Managemant

 

[Guest_imported]

Doesn't matter where the executable is. The slowness seems to come when opening shared dbf files.

Pertti

 

[sharder]

Thot: Take a look at the network packet sizes. Win2k assumes a packet size (TCP/IP) of 8k where NT4 assumed a size of 4k. Certainly in mixed environments, I've seen this to be an issue, and forcing the Win2k box down improved performance considerably.