SQL disk usage seems very high

M

Marcus Pierce

We just started rollout of Project 2002 Pro and Server, so we only have 5 of the 300+ projects that we will eventually put on the server. When I check the disk usage for my database it reads that I am already at 116MB. Four projects have an offline filesize range of only 200-400k, and one exception was at 2.4MB. Our enterprise resource pool, however, contains almost 1000 resources, and we have a couple of complex custom enterprise outline codes (eg, our RBS has 600 entries in the lookup table). Does anyone know if this is what is using so much disk space? Is there anything else in there that I don't know about? Since all of this enterprise stuff is set up and will not be significantly changed, can I assume that disk consumption will now only grow by the amount of projects that we import

Any help is greatly appreciate

--Marcus
 
B

Brian K - Project MVP

Marcus said:
We just started rollout of Project 2002 Pro and Server, so we only
have 5 of the 300+ projects that we will eventually put on the
server. When I check the disk usage for my database it reads that I
am already at 116MB. Four projects have an offline filesize range of
only 200-400k, and one exception was at 2.4MB. Our enterprise
resource pool, however, contains almost 1000 resources, and we have a
couple of complex custom enterprise outline codes (eg, our RBS has
600 entries in the lookup table). Does anyone know if this is what is
using so much disk space? Is there anything else in there that I
don't know about? Since all of this enterprise stuff is set up and
will not be significantly changed, can I assume that disk consumption
will now only grow by the amount of projects that we import?

Any help is greatly appreciated

--Marcus
Click to expand...

How much of that is the Transaction log? If you truncate the
Transaction log what is the size?

The other thing to think about is that a project stored in a database
format will always be bigger than when it is stored in a nice compact
binary format like MPP files. The data is much more spread out in the
db and formatted to make it easiest to get at, not for making it take
up less space.

Also, at this rate you would be looking at roughly 7 gigabytes for the
full 300 projects and that is not bad. I have seen very large
deployments with databases over 60 gig.

--
___
Brian K
Project MVP
http://www.projectified.com

Project Server Consultant
http://www.quantumpm.com
 
Top