July 26, 2011 at 12:35 pm
How come?
According to Mr. Windows Filesystem, my TEMPDB3.NDL (yes, I use 4 files) is 1,2 GB, but Mr. SQL Server says it's just an innocent 600MB file, 98% empty. Who is right and who is wrong? Why does this happen?
July 26, 2011 at 12:36 pm
How are you getting the size from SQL?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 26, 2011 at 1:08 pm
sys.database_files and SP_SPACEUSED both give me correct numbers.
The error is only is at {right-click on the database in SSMS} -> [tasks] -> [shrink] -> [files]
The numbers there are different.
July 26, 2011 at 1:12 pm
I'm on sql 2K5 SP3 standard 32 bit
and I've seen similar issues. I don't remember if it was for the data or log file(s), but I've seen on several occasions total size @ -50 MB instead of 1+GB
I never pursued this to find a solution.
July 26, 2011 at 1:45 pm
Run DBCC UPDATEUSAGE
Shouldn't be necessary on SQL 2005 SP3+
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply