There are a few cases of edges (outside the obvious disk space problem) where SQL Server will not let you add more rows, not the exact number of rows, but it’s worth mentioning:
you have a column IDENTITYand you get to the end of the range for a data type, for example. 255 for TINYINT, 2 147 483 647 for INT, some kind of wicked number that starts with 9 - maybe the number of inches in the sun and back - for BIGINT, etc. When you try to insert the next line, an error 815 about type overflow will appear. This has nothing to do with the number of rows already in the table, in fact, but rather the number of rows that you have already tried to insert (without reseeding the column IDENTITY). If you have a high percentage of rollbacks (or a large number of successful insertions), you can track the maximum value in this column over time.
, , 2 * 2,147,483,647 . (2 * 2,147,483,647) + 1 1 INT, , 666 . , ( SQL Server , ) 4 , , INT ( , , IDENTITY, , ). , , <shrug> ... .
VLDB, 524 272 . , , , , - - - . , , - - -, . , " " Max Capacity SQL Server , , 524 272 , SQL Server (, , 640 , : -)).
, , , , , . , , .