I am planning to make a software (ASP.NET 4.6.1 MVC with Entity Framework), which does a lot of reading from DB. Therefor I have one database, which contains all global information, projects etc. and now I am thinking to either bring all the content into the same DB but in different tables or to create a DB for each bigger group.
我打算制作一个软件（ASP.NET 4.6.1 MVC with Entity Framework），它可以从DB中读取大量内容。因此，我有一个数据库，其中包含所有全局信息，项目等。现在我想要将所有内容放入同一个数据库但在不同的表中，或者为每个更大的组创建一个数据库。
Now as there is a lot of reading going on, is it bad practise to have the connection information in the main db and then to connect to a different DB? Otherwise I would have the project information in the primary database and the content in a different table on the same DB.
现在有很多阅读正在进行，在主数据库中连接信息然后连接到不同的数据库是不好的做法？否则，我会将主数据库中的项目信息和同一数据库中不同表中的内容放在一起。
Are there any notable delays to connect to a different DB to retrive the information?
是否有任何明显的延迟连接到不同的数据库以检索信息？
1 个解决方案
#1
0
If it's all your data, for your application, it should all go in the same database. Definitely use different tables. You should read up on entity design and normalization... and if you really need to do that, you may already be in over your head.
如果它是您的所有数据，对于您的应用程序，它应该都在同一个数据库中。绝对使用不同的表。你应该阅读实体设计和规范化......如果你真的需要这样做，你可能已经在你的头脑中。
#1
0
If it's all your data, for your application, it should all go in the same database. Definitely use different tables. You should read up on entity design and normalization... and if you really need to do that, you may already be in over your head.
如果它是您的所有数据，对于您的应用程序，它应该都在同一个数据库中。绝对使用不同的表。你应该阅读实体设计和规范化......如果你真的需要这样做，你可能已经在你的头脑中。