Global file size

[AnthemAZ]

This company is adding a large amount of items to the global file in order
for third party software to analyze schedules. ie, filters, views, tables,
modules etc.

They are creating numerous customized fields and renaming them to accomodate
the add in software.

My question.

What is the limit on the global file before we experience performance or
integrity problems?

I ran into this a few years back when my files go too large and very slow to
work with because my global file was too large.

I'm trying to caution them on this practice.

Should I be concerned?

Thanks,

 

[Jack Dahlgren MVP]

You should be concerned about too many custom fields. If you are using
Project Server, large numbers of custom fields can cause performance
problems.
I don't think there is any exact number where it becomes a problem, but it
is always a good idea to minimize them as much as possible.

Filters, views and tables are usually a big deal though.

The problem with custom fields is that a value is stored for each task,
assignment, resource in the project, so it can be a large amount of data.

-Jack Dahlgren

 

[John]

You should be concerned about too many custom fields. If you are using
Project Server, large numbers of custom fields can cause performance
problems.
I don't think there is any exact number where it becomes a problem, but it
is always a good idea to minimize them as much as possible.

Filters, views and tables are usually a big deal though.

The problem with custom fields is that a value is stored for each task,
assignment, resource in the project, so it can be a large amount of data.

-Jack Dahlgren

Jack,
In your third paragraph I think you meant to say, "Filters, views and
tables are usually NOT a big deal though." That is, they don't add a
significant hit to performance.

John

 

[Jack Dahlgren MVP]

Yes, I dropped that word by accident. They are NOT a big problem.
Of course, if there were a huge number of them maybe it could be a problem.

-Jack Dahlgren