valentinas

108 reputation

	108 reputation	bio	website		visits	member for	1 year, 1 month
3 badges		location	Wellington, New Zealand		seen	Mar 15 at 0:58

7 Actions

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	awarded	Supporter
May 7	awarded	Scholar
May 7	accepted	Which is better for long term database scalability: adding columns or having key/value store
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!
May 7	awarded	Student
May 7	asked	Which is better for long term database scalability: adding columns or having key/value store