Number of records Vs Table Size

  • Hello firends. I was analyzing my dtaabases and found that there are many tables which have less number of records with occupying size as compared to the tables having huge number of records but will almost same size. Can there be some issue with those tables with few records ? For example I have one table with 26000000 records occupying 5874 MB space and 9000000 records table occupying 6067 MB space. Number of columns are almost same [not exact but almost].

  • It isn't the number of columns that determines how much spacea row takes in the database, but the size of each row plus the fill factor used on the table.

  • Can anyone tell me if this behaviour of table is fine or do we need to sort out some issue.

  • Lynn already answered. It depends on the data involved and the fill factor on your indexes. simply a count of rows and columns doesn't tell us anything. You can have 15 columns in a table that are int and 15 columns in a different table that are varchar(150) and exactly the same number of rows in each. The int table will be much, much smaller than the varchar table because the data is just bigger in the second table.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply