108 reputation
3
bio website
location Wellington, New Zealand
age 27
visits member for 2 years, 3 months
seen Sep 22 '13 at 23:16

May
17
comment Which is better for long term database scalability: adding columns or having key/value store
If I could choose another platform (not standart MySQL/TSQL), then I would probably go with some document database, ravenDB, google App Engine or similar, but that's not the case. As for plan A: do you have any references that would confirm what you're saying? For me this sounds like a really bad practice - the data that I will have would probably fall to nvarchar(100) type and placing that in blob (and loosing ability to query over it) sounds like a really bad idea.
May
7
comment Which is better for long term database scalability: adding columns or having key/value store
It's pretty much like sys.configurations. Not trying to have flexible schema - I think that's what document oriented databases are for. Good point about defaults and data type, thanks!