(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!
Back in 2009 I started posting a summary at the end of the year of what I read during the year and people have been
(Yes, this is for last year!) Back in 2009 I started posting a summary at the end of the year of what I read during
It’s the time of year again where companies do crazy sales on the day after Thanksgiving in the US, and we’re doing the same! All
Happy Fourth of July to all who celebrate! I’m looking forward to a great view Thursday evening looking west along the Skagit Valley with some
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.
4 thoughts on “Weekly survey: large-value character storage”
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?
Aaabsolutely. I’ll go into all the details in the accompanying editorial next week. But Shhh – I’d like to see what people vote.
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.)