Geek asks and answers

What is the most scalable design for this table structure

DataColumn, DataColumn, DateColumn

Each so often we put data in a table by date.

So, at first everything seems wonderful, but then I thought: what happens when there are a million or a billion rows in a table? Should I split tables by date? So query performance will never get worse? How do people deal with such things?

+3
source share
6 answers

You can use partitioned tables starting with SQL 2K5: Split tables

Thus, you get the benefits of ensuring a clean logical design by being able to move old data to another group of files.

+3
source

- . , ..

. , . [DateColumn], , [DateColumn]. , [DateColumn].

, .

+2

, IMHO db, / .

, , DateColumn. , / , . ( , .)

0

, . , , .

0

, , .

Microsoft SQL Server 2005 . SQL Server 2005 , .

, , .

: SQL Server 2005, (, OrderDetails), , . , , SQL 2005 , . SQL Server 2005 .

SQL Server 2005

0

, . : , . , .

. . , , .

, .

.

(NB - , , , , , .)

0
source

More articles:


All Articles