G
Gizmo Gizmo
Hi.
Having problem with Project Server Database size when importing
assignment through VBA program I've created.
Importing a project with 105 tasks each having 5 resources assigned
with assignments spanning from jan 2004 to dec 2004. Together 1100
(man)-month with actual work data.
The problem is that the filesize (used space) of projsvr_data.mdf grows
with appr. 150 MB and projsvr_log.ldf with 200 MB.
It seem to me that this is an unnatural growth in db growth for those
assignments and the problem is that the customer has 100+ projects that
is going to be imported to Project Server.
(I have even tried to enter this project manually in Professional but
result is the same.)
Configuration is MS Project Professional/Server 2003 on a Win 2003
running SQL Server 2000.
Is this normal? Or is there some settings that will affect this
situation in a positive direction that I've overseen?
Thanks.
Having problem with Project Server Database size when importing
assignment through VBA program I've created.
Importing a project with 105 tasks each having 5 resources assigned
with assignments spanning from jan 2004 to dec 2004. Together 1100
(man)-month with actual work data.
The problem is that the filesize (used space) of projsvr_data.mdf grows
with appr. 150 MB and projsvr_log.ldf with 200 MB.
It seem to me that this is an unnatural growth in db growth for those
assignments and the problem is that the customer has 100+ projects that
is going to be imported to Project Server.
(I have even tried to enter this project manually in Professional but
result is the same.)
Configuration is MS Project Professional/Server 2003 on a Win 2003
running SQL Server 2000.
Is this normal? Or is there some settings that will affect this
situation in a positive direction that I've overseen?
Thanks.