Faster way to find Row count of a table in SQL Server

In SQL Server 2000, normal way of finding the total number of records in a table is by using Count() function. Though it would give the exact result, it has a performance issue. Its because it would do a table scan on that table.

i.e, Select count(*) from Authors --- This would do a table scan on Authors table.

The work around is to fetch the number of records from SysIndexes table. But please be adviced that though it would be faster, the number of records returned would not always be perfect. Only if the database has uptodate statistics it would show the exact count.

i.e., Select Rows from SysIndexes Where [ID] = Object_ID('Authors') And indid < 2

Moreover it is not advisable to query the Sytem tables directly. It's because if Microsoft changes the schema of this SysIndexes table in future all your existing code won't work.

In SQL Server 2005 they have come up Partitioned Table concept. So its pretty easy to find the row count of a table without using Count function.

Select Sum(Rows) from Sys.Partitions Where Index_ID < 2 and Object_name(Object_ID) in ('Sales')

It is not necessary that we need to have upto date statistics for this.

Technorati tags: SQL, SQL Server 2005, SQL Server 2000

Comments

Anonymous said…

cool....

12:31 AM, September 27, 2007

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of ...

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As" ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul...

AWS fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request

While using AWS and trying to copy a file from a S3 bucket to my EC2 instance ended up with this error message. Command Used: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ Error: fatal error: An error occurred (400) when calling the HeadObject operation: Bad Request The error goes off if we add the region information to the command statement. I am using Asia Pacific (Mumbai) so used ap-south-1 as the region name. Modified Command: aws s3 cp s3://mybucketname/myfilename.html /var/www/html/ --region ap-south-1

Vadivel's blog

Search This Blog