.net - Are there advantages to dividing application databases by usage pattern? -


I am working on an application that has two different audiences and as such there are two different types of data. On the side there is too much read / under-written meta data. In these tables, a relatively low line will be counted and most of the applications will be read on the other side.

On the other side of the application is very close to high-writing / low-read behavioral data. There will be a lot of velocity on many figures and inserts here. This part of the application will read some data from Meta, but nothing will be written back on that side.

There will be no need to have an RI between these two buckets of tables.

My question is this: Does it make sense to create two different types of different types of these different types? Information? What are the advantages and disadvantages of both methods?

If it matters, then it is built using SQL Server 2008 Back-End.

I recommend taking the time to ensure that the design is in such a separation in future Do not interfere, but implement it as a single database.

It smells of optimization ahead of time, there are very high level database servers that can perform equally well under high load. However, there are ways to replicate that can be done in the form of multiple servers with custom data replication, or can use the same physical memory via back-end data fiber.

I think you should work to avoid this early start in the implementation of your project in a lot of unnecessary but it will be done in the future (through classroom design, 3-level architecture, or even database To complete the stored procedures (icky), a method will not take much time to use.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -