Mcgillivray, Donald [ITS]
donald.a.Mcgillivray at mail.sprint.com
Wed May 19 16:06:05 CDT 2004
Hello, All I'm working on a system that monitors a set of folders for the appearance of text files matching specified profiles. When files are detected, they are moved via FTP to the db's environment and ingested - either the entire file or just the first record, depending on the type of file - into a temp table in the db. Once the data is in the temp table, it is processed by performing a variety of summary queries and appending the results to a series of permanent tables. The temp table is then purged and the cycle is repeated. It had been my intention to leave this db running round the clock capturing and summarizing data, but I was alarmed after allowing it to run all night to find that the db had bloated to about a gigabyte by this morning. After halting the capture process, I compacted the db and its size came down to about 55 meg. I'm not real hip to all the factors that contribute to bloat, so I'm interested to learn which practices exacerbate the problem and which ones mitigate it. I'd also be interested in techniques to get rid of it via automation once it appears in my db. Running Access XP on Win2k. Thanks! Don McGillivray Sprint Mailing Services Rancho Cordova, CA