> One big problem with Access is that databases don't shrink as data is > deleted, and there's nothing in Access equivalent to the database/file > shrinking options that, for example, MS SQL Server has.
What about Compact/Repair Database? So, you might end up > with a very large, very sparse database file with a few hundred rows of > actual data. Using Access as a storage location for CF Client variables will > often result in this problem. > > A bigger problem than sheer file size with Access is how it handles > concurrency - or doesn't handle it, to be more precise. Locks are placed on > tables in Access, so if you have a large Access table that everyone needs to > read, and someone's writing to it, everyone gets to wait. > > In the end, I think that your hosting company's requirement is probably a > good general rule, especially in a shared server environment. It might be > the case that your 750MB file works well enough for you, but if everyone on > that server did the same thing ... > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > > Fig Leaf Software provides the highest caliber vendor-authorized > instruction at our training centers in Washington DC, Atlanta, > Chicago, Baltimore, Northern Virginia, or on-site at your location. > Visit http://training.figleaf.com/ for more information! > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232020 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
