PS2003 Database Question - Newbie Question

[Pako]

Hi,

I have just instaled Microsoft Project Server 2003, and I have a
question.... I think it must be a silly question, but I need to know.

My company mannage 100 projects per year (I don´t know exactly), and I
have red that I can do partitions of the database. Why? Which are the
benefits of doing that? Where can I read more about that?

Thanks in advance

Pako

 

[Doug]

Pako:

I'm not sure what you mean by doing part of the database. Installing
Project Server will create the required database objects, and that is much
better than you trying to create them.

Project Professional and Server can easily handle many more than 100 projects.

Please explain further what your question is.

Doug

 

[Gord Schmidt]

Hi Pako,

Database partitioning is used for scaling Project Server; that is, to allow
higher usage volumes. I'm guessing that if you don't know what it is, you
probably don't need it.

Gord

 

[Rod Gill]

Partitioning is also useful when you have two completely separate groups of
projects that need to managed/administrated separately. Or one group can
require very high security. By partitioning it looks like that team has
their own copy of Project Server so they can lock down exactly what they
need.

I doubt you need to do this. Limiting access to different projects is can
easily be implemented using the RBS code.

 

[Pako]

Good Morning and thanks to all for answering so fast.....

...actually, I don't know how many projects has my company because I
started to work here two months ago here.... I only know that the company
has exactly threee type of projects... Trains, Electrical Lines and Solar
energy.... and If I have red well, I think It would be interessant If I
partition the database in three parts...

Could It be? What mut I read to do that? When could I do that?

Thanks again

Pako

 

[Michael Samadi]

Hi Pako

Actually Database partitioning in Project Server 2003 is very useful at
spreading the loads across more than one physcial location which lessens the
load on any one SQL server. However this is a scaling out ability of Project,
but you need to determine what your loads will be on your environment. Having
100 projects is only one piece of the information. Things like how many
users, what they will be doing and how many concurrent users will be on it
are some other numbers you would have to identify.