|
|
Posted by Greg D. Moore \(Strider\) on 02/19/07 16:25
"Dylan Parry" <usenet@dylanparry.com> wrote in message
news:45d9c6ef$0$765$bed64819@news.gradwell.net...
> Hmm, now I think this might be where I discover some problems! I've just
> checked the database and it purports to be 4.5GB in size. Now if I view
> each of the tables and add up their respective sizes, it comes to less
> than 400MB (not including indexing). So something doesn't seem right
> here...
>
Ok, 4.5 GB database is trivial.
You mention 400 MB not including indexing. How much are indexes taking?
Also, if you're not doing transaction log backups, or aren't in simple
recovery mode, much of that could be your log file.
>> How much memory does the server have?
>
> It's got 1GB RAM.
Well, assuming a 400MB db, I'll guess you've got a pretty good cache hit
ratio, but take a look at that and see what you get.
>
> --
> Dylan Parry
> http://electricfreedom.org | http://webpageworkshop.co.uk
>
> Programming, n: A pastime similar to banging one's head
> against a wall, but with fewer opportunities for reward.
--
Greg Moore
SQL Server DBA Consulting
sql (at) greenms.com
Navigation:
[Reply to this message]
|