November 24, 2008 at 8:01 am
Howyadoin,
I've been brought in to shepherd a back-end migration from Access 2000 to SQL 2008 Express. The Access back-end is terribly overloaded (~30 users) and is constantly hiccupping, therefore I'm going to SQL.
The server on which Access currently resides is running Win2K Advanced Server and the drive has (to my surprise) drive compression and indexing service enabled. In my past experience, both are generally considered bad in this sort of application. Is there a valid reason to have these enabled?
Thanks,
-Mark P.
November 24, 2008 at 8:45 am
Compression makes sense to save space, but if you're that tight on space, the read/write from a DB will be problematic. If you can spare the space, I'd uncompress.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy