INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Jobs

Backend Bloat

Backend Bloat

(OP)
I have a backend database that has been observed bloated it the 390 MB range and on compact is under 7 MB.

I am well aware of the difference in record locking and not and record locking is turned on.

Interestingly the file after compact was 6600 KB. Then I ran a particular process that adds records (<100) amongst 4 tables. After this process it shot up to 113,764 KB. Then compact and down to 6680 KB. Next I stepped through the same code and it grew to 6948 KB. A subsequent compact and down to 6720 KB. This latter test is in line with what I would expect, a few extra hundred k for record locking. Now I have been unable to repeat the first crazy growth. Any thoughts on what causes this sort of thing or may be intermittent?

I suspect something about code but rather than a general go implement best practices direction, I was hoping someone had some specific thoughts on what to fix first.

Typically this is a multi-user system but my test was done with a copy of the BE / FE locally and attached locally.

As a side note we recently ran across a similar issue for Front ends when a recordset is not closed properly.... Access recompiles the code multiple times, bloating the file. A reason I tend to look first at legacy code.

RE: Backend Bloat

(OP)
It is repeatable... Compact the source copy backend get the 6660 KB file (oops I was off 60K when I typed) and then get the huge growth...

Now the weird part compact the 6660 KB file... get a 6652 KB file... run the same process again... 2 out of 3 times the database bloat is hundreds of KB as expected.

RE: Backend Bloat

(OP)
After checking other systems with the same code, this seems to be anomalous rather than the rule. I am chalking it up to sometimes bad things happen in the computing world. I still suspect the compiler and code not being less than ideal.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Resources

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close