Database Partitioning in SQL Server 2005

My project modules are organized in such a way that I have to maintain the following database structure.

I have 5 schemes, each of which contains from 20 to 50 tables. Each scheme is associated with one project module.

All tables that are used in several modules are stored in the "COMMON" schema. Each module takes from 2 to 5 months.

So, when the first module is finished, we open it for use and continue with the second and so on. Meanwhile, real data is inserted into the circuit of the finished module. In addition, the definitions of the tables of the finished schema may vary slightly depending on corrections and suggestions about errors.

I want to be able to backup / restore, synchronize the database schema according to the schema (I think this is called vertical partitioning?)

In DB2, there was a way to place tables in different table spaces and back up / restore table spaces separately.

I am looking for similar or better solutions to a problem in SQL Server. So the problems are:

  • How to apply the definition of a change table to a table that contains real data.
  • Ability to update / modify / restore / backup / synchronize database schema according to the scheme

Any advice is appreciated.

+3
source share
2 answers

- SQL Server, SQL Server . db , . .

+1

, , . : , .

, . SQL Server, . VLDB, / . , / , , .

, , , , : SQL-, , .

, ALTER TABLE, , , , , ( ), / . , .

0

Source: https://habr.com/ru/post/1733888/


All Articles