I have a table storing property data for thousands of properties, all coming from a feed. (updating at least once a day).
I'm certainly not an expert with databases and would appreciate some guidance on the best way to approach building the property table. The challenge is that each property has a LOT of attributes which might or might not be included. Each attribute value is potentially unique, so a relational table doesn't seem like it would provide any benefit.
Currently, my plan for the table is simple, creating a wide table with a lot of potentially NULL columns. eg:
id - int(not null) date - datetime(not null) attribute1 - varchar(null) attribute2 - varchar(null) attribute3 - int(null) attribute4 - bool(null) ect..
Is there a better way to set this up? Each attribute is uniquely associated with the property, so keeping it all in a single table make sense to me.
Will having that many columns, even if most are NULL, cause me issues when thousands of records exist in that table? Each day, I need to do select several select queries on this table, returning hundreds to thousands of records each time.
Any advice or direction on what to research is greatly appreciated!