Single .mdb for component database

Permanently deleted user

• July 22, 2016 19:26

As I have been working with Zuken I downloaded a few manufacturers databases and see that they are able to combine the component, symbol, and configuration databases into a single file. I had originally copied the Own... databases an renamed them but it means that I have a lot of separate database files and a more confusing setup. So I have a few questions to go along with this.

Is there a way to combine the databases I already created?

How do I create a single database file like the manufacturer ones for in the future?

What is the benefit of using separate databases?

Thanks,

Was this Helpful?

0

• 

  Permanently deleted user

  • July 22, 2016 19:27

  I never had the opportunity to copy databases but Zuken has a tool that for copying from one database to another, or to create a single database. I think its called DBTool. I'm not sure if the tool is automatically installed when you run the installer. I think with that tool you could create a seed database to store everything in one MS Access file.
  
  The benefits for a single file E3 databases is portability. However, it's not a good long term solution. Ask any database administrator. If the file gets corrupted, you are screwed! So you would need to back it up and periodically run the Access tool to compact and repair the database.
  
  MS Access databases have an upper limit of 2GB and its conceivable that you will run out of room. If you split up the database into individual databases (i.e. Component, Symbol and Configuration, then you some room to grow. I'm guessing that you'd max out the Symbol database first since it has a lot going on vs the Component and Configuration databases.
  
  The ideal solution is to use either Oracle or SQL Server as your E3 database. Keep everything in a single database.
  
  The benefit of maintaining separate databases (albeit a small one) is that it is possible to have different symbol/configuration databases where you could swap out ANSI symbols vs IEC. In other words, the same component could look different depending on how you configured the database connections. I'm not sure of the practicality of maintaining two sets of symbol/configurations.

  Was this Helpful?

  0

Please sign in to leave a comment.