Manual Caching and Automatic Caching for Programs - Page 2

 By Brien M. Posey
Page 2 of 2   |  Back to Page 1
Print Article

The other major problem with caching programs is that not all programs can be cached successfully. For example, suppose your organization has a proprietary order-entry program that acts as a front end to a database. If a mobile user attempts to cache this program, she may or may not be able to do so successfully, depending on how many of the necessary databases and indexes she accesses. Another factor is how many other users are accessing the database while the mobile user is attempting to cache the database. If information in the database is constantly changing, then the databases and indexes may be out of sync with each other by the time the caching process completes. Likewise, if the user makes changes to the database while offline, Windows 2000 will attempt to synchronize those changes when the user reconnects. The synchronization will be unsuccessful, because Windows synchronizes offline changes at the file levelbut database synchronizations are usually performed at the record level, rather than at the file level.

Finally, there's the issue of size. Even if you could guarantee that no other users would touch the database from the time you began caching it to the time you reconnected to the network, there's a good chance that you wouldn't be able to cache the necessary databases because of their size. After all, you can't cache a 20 GB database on a laptop that only has a 10 GB hard disk space. As you can see, caching programs presents some serious problems. If possible, it's usually better to simply load a program locally onto a laptop's hard disk than to try to cache it.



As I've explained in this article, there are issues to consider when you attempt any type of caching. Now that you understand how caching works and what the issues involved are, I'll conclude the series in Part 3 by explaining how to enable caching. //

Brien M. Posey is an MCSE who works as a freelance writer. His past experience includes working as the director of information systems for a national chain of health care facilities and as a network engineer for the Department of Defense. Because of the extremely high volume of e-mail that Brien receives, it's impossible for him to respond to every message, although he does read them all.

This article was originally published on Dec 19, 2000
Get the Latest Scoop with Networking Update Newsletter