You’ve got questions, we’ve got answers.
No, not Radio Shack – Twitter. Right now, no matter when you’re reading this, there are people on Twitter who can answer quick questions for you. Thanks to an excellent idea by Aaron Nelson (Blog – @SQLVariant), it’s even easier now. In this post, I’ll show how to ask questions and how to answer them.
How to Ask #SQLHelp Questions
Sign up for a Twitter account. You don’t have to follow anyone, but if you want to, I’d suggest following my SQL Server Twitter list instead of individual people. I’ve got a post on how to use Twitter lists, but in a nutshell, they let you keep in touch with a lot of people who focus on a particular topic. The cool part is that their tweets don’t clutter up your main Twitter page, which is important because there’s several hundred SQL Server folks on Twitter as of this writing.
When you need help, write a tweet and include #SQLHelp in the tweet, like this:

Asking a #SQLHelp Question
If your question involves more than 140 characters, you’ve got a few options:
- Post a question to StackOverflow if it’s a programming question, to ServerFault if it’s an infrastructure question, or DBA.StackExchange.com if it’s a SQL question. Tweet the link to your question.
- Upload screenshots to TwitPic. It’s a free service that tweets the images you upload. When you write the description, make sure to include #SQLHelp so that the smart folks see it.
- Upload files to FileDropper.com and tweet the link to the file. Remember that anything you upload is public – don’t upload your databases. It’s a great way to show query execution plans though.
After you click Update to post your question, click on the @YourName link on the right side of your Twitter home page. For me, it says @BrentO, because that’s my Twitter name. This page is your replies page – it shows anyone who’s mentioned your name. Then sit tight – as people reply to you, you’ll see the new tweets on this page.
When you reply back to users, the default Twitter action is to put their @Name at the beginning of the tweet. Edit the tweet first and put a period and a space before their name, like this:

Public Replies on Twitter
This is because if you just start the tweet with @Mike_Walsh, then the only people who will see it are the folks who follow both you and Mike. If you start the tweet with anything other than an @ sign, then anyone who follows you will see your reply – regardless of whether or not they’re following Mike.
Don’t include the #SQLHelp tag in the reply, either. That just helps keep the #SQLHelp search cleaner.
When you get your final answer, post it a thank-you back to #SQLHelp, like this:

Got My #SQLHelp Answer
That way people know when your question is answered. If your question hasn’t been answered within an hour, you can repeat it again, but please don’t repeat it in less than an hour.
How to Answer #SQLHelp Questions
Set up a search in your Twitter client for #SQLHelp, or use one of these alternate methods:
As you’re interacting with the questioner, remember that they’re probably new to Twitter, and that you’re probably not the only one working with them. I open up two web pages – Search.Twitter.com with a search for the questioner’s username (so I can see who’s replying to them) and the questioner’s Twitter page (so I can see everything they respond back). That way you can keep duplicate interactions to a minimum.
Thanks again to Aaron Nelson (Blog – @SQLVariant) for suggesting this! I think it’s a great way for the community to get even more involved in real time.
David Stein December 18, 2009 | 9:16 am
I wondered why you guys kept replying in Twitter with .@brento.
Makes sense now.
Pingback: Need #SQLHelp? Throw up the Bat-Signal | The SQL UPDATE Statement
Jon Crawford December 18, 2009 | 9:22 am
Alright, you got me, I’m finally tweeple now. Or does that make me a twit?
Mike Walsh December 18, 2009 | 9:24 am
Haha. I like the test case tweets, Brent
Great idea. I’ll enjoy following that hashtag. To be honest, I don’t answer much on serverfault or stackoverflow or even the msdn forums because typically by the time I hit the site there are a lot of answerers already. In twitter even without the hash tag I’ve been able to be a part of a task force helping folks’ problems. Following this tag will make it easier.
Brent Ozar December 18, 2009 | 9:25 am
Hahaha, I thought you’d like those…
Pingback: Got SQL Server Questions? | SQL Server Blog - StraightPath Solutions
Pingback: Weekly Link Post 124 « Rhonda Tipton’s WebLog
Pingback: Link Post 124 « Rayet’s Blog
Colin December 31, 2009 | 10:13 am
Brent, Thanks a lot. I am still somewhat of a jr. SQL Server DBA and I also do Oracle and Sybase. This will help a lot I think and because of this I finally had to give in and start tweeting.
Thanks for all your posts they have been a big help to me.
Brent Ozar January 2, 2010 | 8:06 am
Cool, glad I got you started!
Pingback: The SQL MVTweep Awards ! (#sqlMVT) « mikeSQL's Blog
Pingback: Top 10 SQL Resources on the Web « SQL Feather and Quill
Pingback: Please Join Us for #PoShHelp – SQLvariations: SQL Server, a little PowerShell, maybe some Hyper-V
Pingback: Moving SharePoint to the data center – JohnSterrett.com
Pingback: Oracle Vs SQL Server | 140,000 Characters or Less
Pingback: Aaron Bertrand : Useful, free resources for SQL Server
Pingback: Getting SharePoint help #SPHelp | Thomas Vochten
Pingback: SQLU DBA Week – DBA Progress Report | StraightPath Consulting's SQL Server Blog
Pingback: Hello world! helpwithdotnet is alive « DotNetHelp
Pingback: Use #AccessHelp on Twitter for quick support help. | Access Help and Tips by AccessExperts.net
Pingback: Changes Aren’t Permanent But Change Is | The SQL Agent Man
Justin Dearing July 13, 2011 | 12:50 pm
Brent,
Perhaps this article should be updated to reflect include dba.stackexchange.com in addition to stackoverflow.com as a place to store questions. Also, I think gist.github.com and pastebin should be mentioned as places to store (broken) example code.
Brent Ozar July 13, 2011 | 1:11 pm
Justin – great idea! Done.
Justin Dearing July 13, 2011 | 10:21 pm
Awesome!
Minor grammatical nitpicking, shouldn’t the to preceding “ServerFault” be removed?
Pingback: SQL Server Resources | Question Driven
Pingback: SSIS Junkie : Bootstrapping SQL Server bloggers and blog readers with Twitter!