What causes a database file size to bloat (file size increase)?

[The_Doc_Man]

I think that is a fairly common situation. Many database administrators subscribe to hating Access. Some because they have seen troubled caused by Access dabblers who haven't got a clue what they are doing but many just to be part of that culture,

Many more of them just don't understand Access and its inherent dynamics that are a bit different than "the big boys." Because Access uses SMB protocol, which is the same exact protocol used for Windows File and Printer sharing, they can't fire-wall without extra work. Otherwise, nobody could use a network printer or network-attached storage. They feel like they are losing control. I (regrettably) had to use office politics to get my government supervisor to tell IT to get out of the way of a necessary internal application we used for tracking the status of our (over 1500) servers. They HAD to relent when we pointed out that we could give them detailed patch status and patch history AND detailed reasons for patch delays. After a while, they caught on that it wasn't such a bad thing. But it took a bit of juggling to get them to back down.

 

[Pat Hartman]

Why is it more expensive?

Because you need a DBA to manage it. Application developers know enough about SQL Server to be dangerous. They don't know how to optimize it or ensure that backups are timely and usable for starters.

As others have mentioned, temp tables are best stored in a separate disposable database. That way, you only have the bloat you created since the last time you started an import process.

 

[Thales750]

Because you need a DBA to manage it. Application developers know enough about SQL Server to be dangerous. They don't know how to optimize it or ensure that backups are timely and usable for starters.

As others have mentioned, temp tables are best stored in a separate disposable database. That way, you only have the bloat you created since the last time you started an import process.

Gave up on that idea years ago. Now all "temp" table are permanent SQL tables that are kept organized by using the Computer Name, or the user Login. Depending on how the system is setup. I prefer Login because they are portable.

 

[Pat Hartman]

Gave up on that idea years ago.

If the BE is SQL Server, makes sense to use temp tables in SQL server if you actually need temp tables but if the BE is Jet or ACE, then the "side-table" solution is the best since you absolutely do not want to join Jet/ACE to SQL Server just because you can.