MS Access Database on a Compressed Network Drive 3

[rustychef]

Ive been trying to tweak a few office databases that reside on a network drive. Recently they seem to have gotten slower on startup (found that refreshing/verifying the linked table strings is the biggest culprit here) and during activities such as searches and saves.

I just noticed today that the network drive the databases are on has been compressed.

Can anyone tell me if this is a big issue? Should I have the database directory returned to an uncompressed state? From what I understand, when accessing information on a compressed drive the data has to be uncompressed before it can be read, and recompressed to save it.

The user workstations are XP, and Im unsure of the Server OS but I believe its in the Windows_NT family. Users are accessing the database backend on the server with the frontend on their desktops.

 

[Remou]

A compressed drive is not a good place to keep databses.

 

[MikeC14081972]

Remou,

Could you expand on that as I'm having issue at a client site and I believe the drive may be compressed (what's the easiest way to confirm this?)

Thanks

http://www.hanlew.co.uk

 

[rustychef]

First of all, Thanks for the answer Remou.

Secondly, for MikeC14081972:
Quickest way to check for a compressed file/directory is to see if the text it BLUE instead of black.

If you want to be sure, right click on file/directory select Properties, Click advanced button, and under "Compress or Encrypt attributes", see if the "Compress contents to save disk space" box is checked.

 

[Remou]

One of these may help:

http://support.microsoft.com/kb/193051

http://www.vbforums.com/archive/index.php/t-397155.html

 

[Remou]

This is why it is not a good idea to store databases on compressed drives:

http://support.microsoft.com/kb/251186/en-us

 

[MikeC14081972]

RustyChef - you confirmed my thoughts, thanks

Remou - Thanks for the link.

Stars all round.

http://www.hanlew.co.uk