December 4, 2006 at 4:33 am
December 4, 2006 at 1:12 pm
I beleiv it is sql BUG...
You can make use of the following scripts...
http://www.databasejournal.com/scripts/article.php/1450801
http://vyaskn.tripod.com/sp_show_biggest_tables.htm
MohammedU
Microsoft SQL Server MVP
December 4, 2006 at 1:13 pm
Try also sp_spaceused procedure after DBCC UPDATEUSAGE...
MohammedU
Microsoft SQL Server MVP
December 5, 2006 at 12:46 am
Thank you Uddin..
I have one more issue plzzzzzz.....
one day our transaction Log size(physical size) grown to 2GB and a day after when I see it has come down to 1.4 GB(we did not perform any shrink operation)...
According to some books without DBCC SHRINK or explict shrink operation Log physical size will not b reduced...
Do you know any reason for that size fluctuation..
Thank You
Shekhar
December 5, 2006 at 6:31 am
are you really talking about the physical file size or the space used in the log file??
December 5, 2006 at 6:42 am
December 5, 2006 at 6:48 am
Had any traces running when this happened?
December 5, 2006 at 6:55 am
December 5, 2006 at 7:06 am
Profiler.
By your reaction I'll take that as a no .
December 5, 2006 at 7:18 am
December 5, 2006 at 7:38 am
I rarely do too.... but the answer is alway no untill you ask .
December 5, 2006 at 7:46 am
December 5, 2006 at 7:54 am
None... I'm still has baffled as you are. Waiting anxiously to see the conclusion of this one!
December 5, 2006 at 11:00 am
Is AUTO SHRINK is enbaled on the db? If it is disable it.
MohammedU
Microsoft SQL Server MVP
December 5, 2006 at 11:05 am
DOH! always the simple stuff. I never have to on so I seem to forget about it .
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply