InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 19 May 2013 15:07:47 GMT20http://www.sqlservercentral.com/Forums/Topic449921-1181-1.aspxhere is another way to do this without a cursorhttp://www.wvmitchell.com/tips/SQL_table_sizes.htmMon, 26 Mar 2012 12:04:38 GMTWILLIAM MITCHELLhttp://www.sqlservercentral.com/Forums/Topic449921-1181-1.aspxDoug, thanks for the responses. I updated the code by adding the 'TRUE' parameter to the sp_spaceused call (and gave you credit for that - I submitted the updated version and it should be published soon). I noticed that it slowed down performance the first time it ran, and then ran instantaneously on subsequent executions.Fri, 13 Feb 2009 13:12:55 GMTJesse McLainhttp://www.sqlservercentral.com/Forums/Topic449921-1181-1.aspxJessie, I did some searching and found that you should add a param to the sp_spaceUsed proc. This will give you a more accurate value. EXEC sp_spaceused @User_Table_Name,'true' I also used this to get the unused KB's for each tableUnused_KB = CONVERT(int, LEFT([unused], PATINDEX('% KB', [unused]) - 1))Thanks again.Thu, 15 Jan 2009 13:26:27 GMTDoug S.http://www.sqlservercentral.com/Forums/Topic449921-1181-1.aspxJessie, thanks very much for this, but I found something rather interesting, perhaps you can explain. The query identified a table with row count = 154 and phys_size_KB = 26760. However, when I selected all rows I got a count of 202 is this because the statistics are out of date?This table has a high unused allocation of 99%. I calculated this based on unused/reserved. I just ran a shrink on the database and it does not seem to help. Can you explain this?ThanksThu, 15 Jan 2009 13:05:41 GMTDoug S.http://www.sqlservercentral.com/Forums/Topic449921-1181-1.aspxComments posted to this topic are about the item [B]<A HREF="/scripts/T-SQL/62053/">Identify Large Tables</A>[/B]Thu, 31 Jan 2008 06:59:44 GMTJesse McLain