简体   繁体   中英

c# database architecture

I am planning to build an equipment maintenance application. I am going to use C# and WPF with Access or SQL database(s). This single application is going to handle many projects (facilities).

My question is: What is the best approach...

  • create separate databases for each project
  • have one (much more complex) database which will handle all facilities

Unless there is a specific requirement for it to be separate databases, do not separate them. In the end it will turn out to be much more maintenance effort to have all these databases (how do you know each one is backed up and restorable? What happens when the structure changes, how do you apply the changes to each database in a safe way? etc)

What seems complex right now (having a single database) will be much simpler in the long run.

Using single database for the equipment maintenance application would be better. Have a look on below link too as similar scenario have discussed before: Any gain on performance when using single vs multiple databases?

Feel free to ask further questions if arises. Thanks.

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM