Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Max number of rows in table

Author  Topic 

AskSQLTeam
Ask SQLTeam Question

0 Posts

Posted - 2002-07-28 : 15:16:50
Dan writes "Hello,

Is there a limit to the maximum number of rows that a table in SQL Server can hold?

Describing the problem specifically,
We hold several workshops and seminars, we give away awards and scholarships, we have donors, panelists, hosts and attendees in workshops, sponsorers etc. We have a table for clients and a table of descriptors (such as 'host kansas workshop 12/02/01', 'donor-brownscholarship01', 'attendee-albany workshop 02/03/00' etc.). We also have a table that will store the clientids and descriptorids. We have about 20000 cliets currently and about 300 descriptors. Therefore right now there is a possiblity of the client_x_descriptor table having 20000 * 300 rows.
I am concerned that in the future this number may grow in several multiples.

My question therefore is whether there is a limit to the max number of rows that the sql server 2000 table can hold.
I would also appreciate if you could suggest me a way to handle this problem in a different way(probably with a new database design)

I would very much appreciate if you could answer this question.

Thanks in advance,
Regards,
Dan."

robvolk
Most Valuable Yak

15732 Posts

Posted - 2002-07-28 : 15:36:18
Your design sounds good. The client_x_descriptor table is probably the most efficient method, especially in regards to space utilization.

SQL Server can handle many billions of rows, it depends on how much disk space you have available. Assuming that client_id and descriptor_id are both integers, each row will require 8 bytes for storage, so with 6 million rows, this table would require about 48 megs of space. If you index it, you can safely double or triple that amount, which will still keep you under 150 megs, well below SQL Server's limits.

Go to Top of Page
   

- Advertisement -