What's in my project database?

Greetings,

Currently looking into going from Promis.e AutoCad to Promis.e Standalone. Our general questions are what to do with our project database. Do we want to migrate and continue to use our existing database which points to .dwg files? Would we still be able to access and use those in standalone? Should we take this opportunity to go to a new clean database to improve performance?

So basically where I'm at now in trying to answer these questions is that I've connected to a dev database but I don't know where the projects are which it's pointing to. I recall once seeing a Utilities plugin which allowed me to see all the projects in my current database and possibly do some cleanup. Is this Utilities plugin available for 08.11.12.137, and if so can you help me find it?

We are also wondering if there is a general write-up or description of the new multiple database and database-per-project options. If you could provide any links or documents that would be helpful.

Thanks,

Jerry

  • Hi Jerry. There is nothing different about a project database for promis.e for AutoCAD vs. a project database for promis.e Standalone of the same version. Worth noting:

    • Upgrading the database structure to match promis.e 08.11.12.137 would make the database unusable by promis.e for AutoCAD, since the two promis.e versions are looking for different database versions.
    • Upgrading the database structure to match promis.e 08.11.12.137 would still not allow you to access your existing DWG-based projects in promis.e Standalone. These projects need to be "migrated" by backing them up with the "Save files in MicroStation compatible format" option enabled, then restoring them into promis.e Standalone.

    So there's no reason to upgrade your database. I would create a new one instead. See also the Moving From promis.e for AutoCAD to promis.e Standalone article.

    One way to see which projects are in your database is described in this forum thread: Viewing all projects in database with SQL Server Management Studio (hint: you don't need SQL Server Management Studio).

    Regarding database strategy, the following is from Help in promis.e V8i 08.11.12.137:

    Single Database: This option will save all your projects to the same database.  This strategy is recommended if you expect to have many small to medium size projects (<200 pages) that you need to have available at all times rather than archived.  

    Multiple Database: With this option you are allowed to create additional databases and can place groups of projects in each database.  As you select a project in the project manager it will automatically connect to the correct project database that contains that project’s data.  This strategy is recommended if you expect to have many large size projects (>200 pages) that you need to have available at all times rather than archived.  

    Separate Database Per Project: This option requires you to create a new database for each project.  As you select a project in the project manager it will automatically connect to the correct project database that contains that project’s data. This strategy is recommended if you expect to have very few, but very large projects (>1000 pages) that you need available at all times rather than archived. Some features of the software that automatically create new projects such as Project Builder might be inconvenient to use with this strategy since you would have to create a new database before it can generate the project.    If you need to use such features it is preferable to use one of the other strategies.



    Answer Verified By: Gerald Lenza 

  • Matt, you're the best. Dangerously helpful, It's tempting to keep asking questions instead of finding answers on my own :)

    We have about 4000 projects, most with less than 20 pages. Currently we have single database, but we split it into folders by year so each year is <1000 projects. This has reduced the time it takes to open the project manager.

    My first instinct was to go to Multiple Database, one per year/folder, but now I'm not sure that will gain us any performance and may complicate some other processes we have in the building. We'll have to talk about it. Thanks again!