There is no single solution for any case. It depends much on your data structure and application requirements. Most general cases seemed to be as follows:
If your application can't be redesigned and instant access is required to all your data, you need to use more powerful hardware/software solution.
If your application can't be redesigned but some of your data could be count as obsolete because it's requested relatively rearely you can split data and configure two applications to access different data.
If your application can't be redesigned but some of your data could be count as insensitive and could be minimized (consolidated, packed, etc.) you can perform some data transformation as well as keeping full data in another place for special requests.
If it's possible to redesign your application there are many ways to solve the problem.In general you will implement some kind of archive subsystem and in general it's complex problem especially if not only your data changes in time but data structure changes too.
If it's possible to redesign your application you can optimize you data structure using new supporting tables, indexes and other database objects and algorythms.
Create archive database if possible maintain different archive server because this data wont be much necessary but still need to be archived for future purposes, hence this reduces load on server and space. Move all the table's data to that location. Later You can retrieve back in number of ways: Changing the path of application or updating live table with archive table
发布评论
评论（2）
对于任何情况都没有单一的解决方案。这在很大程度上取决于您的数据结构和应用程序要求。最常见的情况似乎如下：
There is no single solution for any case. It depends much on your data structure and application requirements. Most general cases seemed to be as follows:
如果可能的话，创建存档数据库，维护不同的存档服务器，因为这些数据不是很有必要，但仍需要存档以供将来使用，因此这可以减少服务器和空间的负载。
将表的所有数据移动到该位置。稍后您可以通过多种方式取回：
更改应用程序路径
或用存档表更新实时表
Create archive database if possible maintain different archive server because this data wont be much necessary but still need to be archived for future purposes, hence this reduces load on server and space.
Move all the table's data to that location. Later You can retrieve back in number of ways:
Changing the path of application
or updating live table with archive table