SQL Server Performance Forum – Threads Archive
Taskpad vs Properties re. free space on db.
Hi All. When I look at the properties of one of my db’s (using Enterprise Manager) it shows thatsize = 10248 mb
space available = 0 If however I look on taskpad, it shows:
used space = 8350mb
free space = 1290mb Primary space allocated to the db is 9641, and it has auto grow of 100mb. Any ideas about why these two figures aren’t in sync? (My developers jumped up and down when they saw the 0 available, and I struggled to convince them that the space situasion is fine.) 10q.
That is odd, mine match. Silly question, but are your sql sps up to date? Other than that, I am curious to see other responses here. Sorry I could not help! Token SQL Goddess
Life is one fool thing after another whereas love is two fool things after each other.— Oscar Wilde
EM can often show strange results, I don’t normally worry – just hit refresh and try again < grin >
most likely you needed to hit F5.
It’s only on this one db that two does not match. F5 definately not the solution (after many previous "funnies" i’ve learned that this is always the first option, as well as opening and closing EM <img src=’/community/emoticons/emotion-5.gif’ alt=’
‘ /> . SQL Server 2000, SP3a.
Run SP_HELPDB from query anlayzer for any such information on the database, GUI tools are meant to be flaky at times. Check SQL server error log for any information. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
Just to clarify.
In properties, space available mean space actually used by database: primary + log. Not space to grow.
And that value most of the times match with taskpad, first information: Space Available, and match detail taskpad summatory off all grey information.
If what you see is for all databases, I suggest to reaply sp. If is for one particulary database, check error log and run CheckDb and Checkalloc. Luis Martin
Moderator
SQL-Server-Performance.com All postings are provided “AS IS†with no warranties for accuracy.
Run dbcc updateusage(0) in the db and it should go back to normal.
You can’t always trust GUI tools like EM (especially when developers are jumping up and down <img src=’/community/emoticons/emotion-1.gif’ alt=’
‘ /><br /><br />From QA, first run dbcc updateusage(0) to correct any inaacuracies in sysindexes table, and then run sp_spaceused.<br /><br />
I would second Chakri’s suggestion with regard to GUI tools behaviour in the environment, many times in the past I’d faced the trouble and decided to use QA (better) to get optimum results and to get accurate follow as suggested. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS†with no rights for the sake of knowledge sharing.
]]>