growing mdb files

[popodi]

Our Project.mdb and Schema.mdb files have started growing recently. As an example project will start off as a 7MB file and by the end of the week it could grow to 150+. It grows a few megs each time users open any of the applications (DM, I&W). We compact and repair for now, but does anyone know what could be causing it to grow? Thanks!

[PartRidge]

The Project mdb also has link tables back to the master data tables for AutoPLANT. These will take up a large amount. The link tables are used for Bentley's new concept on cahing the data instead of connecting directly to the tables like it was configured for 8.6 and previous.

You can delete these tables and the next time any of the applications connect to the project it rebuilds the link tables.

The Schema mdb or adp if you are running in SQL Schema mode are a little more difficult to optimize. Here you don't want to delete the tables since those are the actual tables. The best I've been able to achieve here is only compacting.

[popodi]

Hi PartRidge and thank you for your response!
We have the data in oracle database. With the "master data tables" do you mean the actual links to those tables? Or is it the few links to the tables that are in the schema.mdb file?

[PartRidge]

It's slightly different if you are using Oracle. The master data tables are those tables on MS SQL or Oracle. If you open the Projdata.adp and select to delete the tables you would delete the actual table on at least MS SQL, I'm not certain it would delete the table to Oracle or not. Not sure if Bentley has integrated the Oracle connection more since I used it last. It use to be that for Oracle if you wanted to make a table structure change you had to do that directly in the Oracle Management Console and update the Oracle View to go with it before going back to AutoPLANT config and register the change in AutoPLANT. This is where AutoPLANT was actually using the Oracle view for the data instead of the raw Oracle table. Never quite understood it completely except that it worked.

[PeterJ]

-Oracle still needs to be edited from Oracle itself (unless you know the trick with the base-project ...).
-With Oracle, no projdata is created, but you can do that yourself through an ODBC connection.
-Schema.mdb has no linked tables. It just holds tables with configuration data and views and reports that are being used by DATA Manager.

[popodi]

Thanks guys!
Just to clarify Peter, in my follow-up question I meant the tables in project.mdb that were linked to schema.mdb. The sentence made sense the first time aroud. :)