(And it's official – this is blog post 39 this month, making this my most prolific month yet for blogging. An arguably dubious achievement…)
In this week's survey, I'm interested in your views on the best way to store large-value character data. I'll report on the results next week (around 4/3/09).
Thanks!
5 Responses to Weekly survey: large-value character storage
Aaabsolutely. I’ll go into all the details in the accompanying editorial next week. But Shhh – I’d like to see what people vote.
Another "it depends".
Off the top of my head, I would want to know:
Define "large".
Do you need unicode or not?
What is your hardware setup?
What is the business need driving this?
Oops. Hope I didn’t spoil your fun.
the new filestream object. that’s my vote. all bets there please. I can’t believe how right i am.
Wait. By ‘large-value’ do you mean font size? (that was a joke.)
[...] week's survey was on how you should store large-value character data in SQL 2005+ (see here for the survey). Here are the result as of 4/3/2009 – and I think my favorite answer is [...]