Are there Performance impacts on having blank attributes on work items?
A customer that has a highly customized RTC workitem process is trying to understand "performance implications" to a design idea.
The Current design has 7 custom work item types, with a well defined parent-child relationship hierarchy of these work item types. (3 levels of hierarchy...not 7).
One of the work item types (in the 3rd level of hierarchy) would have a unique process rule that requires 15 custom attributes to be set. This occurs about 10% of the time. If they add these 15 unique attributes to an existing work item, will the existence of these attributes (but empty 90% of the time) have any impacts on performance or DB size?
The attributes are all small/medium strings.
The Current design has 7 custom work item types, with a well defined parent-child relationship hierarchy of these work item types. (3 levels of hierarchy...not 7).
One of the work item types (in the 3rd level of hierarchy) would have a unique process rule that requires 15 custom attributes to be set. This occurs about 10% of the time. If they add these 15 unique attributes to an existing work item, will the existence of these attributes (but empty 90% of the time) have any impacts on performance or DB size?
The attributes are all small/medium strings.
Accepted answer
Ed,
I would expect additional attribute values to have a minimal effect on the database size. More attributes also has a small performance impact e.g. on loading in the web UI. There is just no free lunch.
However, having said all that, I would not consider that as inhibitor for what you are trying to do.
I would expect additional attribute values to have a minimal effect on the database size. More attributes also has a small performance impact e.g. on loading in the web UI. There is just no free lunch.
However, having said all that, I would not consider that as inhibitor for what you are trying to do.