Recommendation for new database

[Rene Toepfer]

Good Morning,

I need a new, separate, database for an upcoming project.

What is your recommendation for creating them? Would it be better

• to create it from the scratch or
• copy my main database and remove the entries?

If I follow 2, I could reuse the locations partially, the same for keywords (I am aware of that I can export/import them as well).
The metadata sets and versioning are global settings and do not need to be copied.

The main database is error and warning free as per IM analysis tools.

[Mario]

Whatever works for you. If you copy the database, make sure you change its unique id: When You Copy a Database: Change Database ID
I'm not sure why locations are database-specific. There is probably a very good reason because of filters or similar.

[Rene Toepfer]

Thanks, I have copied an existing DB and changed the ID. All keywords, settings for versioning etc. were copied and afterwards adjusted by me.

With location I mean what I have set in the map module.

[Mario]

With location I mean what I have set in the map module.

That's what I meant. Not sure why locations are stored per-database (actually, they are stored and managed in the IMatch database, not in the settings database.
Anyway, the need for an import/export or a non-database specific storage location is probably near zip.

[Rene Toepfer]

I have already two DB but they do not share the locations. If I create a location in DB1 it is not visible (and therfore of course not selectable) them in DB2.

[Mario]

That's what I said. Locations are stored in the database and are thus database-specific.