Hi All
We have a database on our SQL 2005 server that, when running a report for DB Current Size on Disk, displays inaccurate information.
The database file size (MDF) is 91 GB in size. However, in the report, it says it is 815 GB. (Actually, it says it is 815,546.51 MB). Another wierd thing is it says the Tran Log file is "-696,812.63 MB". (The LDF file is about 30 GB on disk). How could that be a negative number? And why would these sizes be so off?
I ran a DBCC CHECKDB, but it came back without problems.
I also ran a sp_spaceused against one particular table in the database (one of the largest ones), and its information doesn't seem right either...
Does anyone know what might be causing these numbers to get skewed so much?
-Ovatvvon :-Q
We have a database on our SQL 2005 server that, when running a report for DB Current Size on Disk, displays inaccurate information.
The database file size (MDF) is 91 GB in size. However, in the report, it says it is 815 GB. (Actually, it says it is 815,546.51 MB). Another wierd thing is it says the Tran Log file is "-696,812.63 MB". (The LDF file is about 30 GB on disk). How could that be a negative number? And why would these sizes be so off?
I ran a DBCC CHECKDB, but it came back without problems.
I also ran a sp_spaceused against one particular table in the database (one of the largest ones), and its information doesn't seem right either...
Code:
[b]name[/b]
CALLS
[b]rows[/b]
93,098,559
[b]reserved[/b]
819,100,104 KB
[b]data[/b]
38,978,880 KB
[b]index_size[/b]
32,397,832 KB
[b]unused[/b]
747,723,392 KB
Does anyone know what might be causing these numbers to get skewed so much?
-Ovatvvon :-Q