Here is more detail
I am using an entity object to track what is essentially an array of N length, where N < 240 (255 is the maximum number of properties available). Each position in the array corresponds with a property name like this:
/* Note: Each number is prefixed by "a" since properties can't start with a number */
public class MyFatEntity
{
public string A01 {get;set;}
public string A02 {get;set;}
// ..
public string A10 {get;set;}
// ..
public string AF0 {get;set;}
}
I require the ability to match a string against any specific position of the array. I plan to use projection with this.
One issue that I forse is that if I create a large fat object with 240 properties, then I am consuming storage bandwidth and creating inefficiencies that don't need to exist.
Not to mention these additional properties, even if null, will count against my maximum entity size. This is not desired since the intrinsic overhead means I'll have less room to save data for longer records.