<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Buck Woody : Questions</title><link>http://sqlblog.com/blogs/buck_woody/archive/tags/Questions/default.aspx</link><description>Tags: Questions</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator><item><title>When you’re asking for help, make sure you explain what you’re trying to accomplish</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/07/22/when-you-re-asking-for-help-make-sure-you-explain-what-you-re-trying-to-accomplish.aspx</link><pubDate>Thu, 22 Jul 2010 12:24:09 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:27232</guid><dc:creator>BuckWoody</dc:creator><slash:comments>0</slash:comments><comments>http://sqlblog.com/blogs/buck_woody/comments/27232.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/buck_woody/commentrss.aspx?PostID=27232</wfw:commentRss><description>&lt;p&gt;At some time, all of us need technical help with something. Whenever you do, make sure you try and frame the question not necessarily in terms of what you want to know, but what you're trying to do. Spending time on thinking through your questions will help you get better answers, and people will appreciate that you're putting some effort into the process, and they are more willing to get help.&lt;/p&gt;
&lt;p&gt;For instance - let's say yo're stuck on a particular SQL Server Replication issue. You're not sure whether moving the Distributor function away from the Publisher server is the right thing to do, given your budget. You could ask:&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#0000ff;"&gt;"Where should the Distrbutor go in a Replication scheme?"&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;That's too vague, and doesn't help others help you. Instead, this might be a better way to put the question:&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#0000ff;"&gt;"I'm setting up the design for my Replication scheme, and I have&amp;nbsp;a limited budget. What are the best ways to save money in my design?"&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;This question goes more towards what you really want to know, and in fact, you may find out that the Distributor question isn't what you need to care about at all. Sure, sometimes you just want the phone number to a store, and you really don't need to tell everyone you're hungry, but if the question goes beyond simple facts, it's a good idea to include as much information as possible so folks can help you best.&lt;/p&gt;&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=27232" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/Help/default.aspx">Help</category><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/Questions/default.aspx">Questions</category><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/SQL+Server/default.aspx">SQL Server</category></item><item><title>Make it Easy for People to Help You</title><link>http://sqlblog.com/blogs/buck_woody/archive/2010/02/08/make-it-easy-for-people-to-help-you.aspx</link><pubDate>Mon, 08 Feb 2010 14:17:59 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:21982</guid><dc:creator>BuckWoody</dc:creator><slash:comments>5</slash:comments><comments>http://sqlblog.com/blogs/buck_woody/comments/21982.aspx</comments><wfw:commentRss>http://sqlblog.com/blogs/buck_woody/commentrss.aspx?PostID=21982</wfw:commentRss><description>&lt;p&gt;OK, there are probably a dozen or more of these kinds of posts, but I’ll dive in anyway. From time to time, people send me e-mails or comments on this blog asking for help. Sometimes it’s on the topic at hand, and other times the topic just jogs their memory about something else. &lt;/p&gt;  &lt;p&gt;Often I’m happy to help. If I know the answer without doing any research (or even if I have to do a little) I’ll interrupt what I’m doing and dash out a note with the answer. But of course I have a job (three, to be exact) and so any time I help with a question I’m lengthening my day, spending less time with my family, and so on. If you think about it, everyone that you ask (and everyone I ask) is in the same boat – when someone helps me, I am taking their most valuable asset: their time. So I learned a very important lesson very early on: Make it easy for people to help you. &lt;/p&gt;  &lt;p&gt;So here’s the steps to follow to do that – it really isn’t that hard:&lt;/p&gt;  &lt;ol&gt;   &lt;li&gt;&lt;font color="#800000"&gt;Request, don’t demand.&lt;/font&gt; I got an e-mail yesterday (on Sunday) where someone found a blog entry about one topic, and basically said this about another topic: “Tell me where I can find ‘x’ so that I can alter it.” Guess what I did? That’s right, I hit the delete key. If you are asking a question from a professional, you need to understand that they normally get paid – very well, sometimes – for their time. Make sure your question is a question, not a demand. &lt;/li&gt;    &lt;li&gt;&lt;font color="#800000"&gt;Be clear about the problem.&lt;/font&gt; Vague statements don’t help – and very few people have the time to dig the real question out of you. Be specific. Ask the single question you really need help with.&lt;/li&gt;    &lt;li&gt;Keep the problem limited. “Rewrite my code for me” isn’t going to happen. “help me with this line” might. “Where do I go to find out more about the SELECT statement” is even better. If your problem takes more than a few minutes for someone to answer, then you should probably get someone on-site to help you.&lt;/li&gt;    &lt;li&gt;&lt;font color="#800000"&gt;Explain what you’ve already done&lt;/font&gt;. This, of course, means you’ve already actually &lt;em&gt;done &lt;/em&gt;something. What have you looked up, what do you already understand, where have you looked, what have you tried?&lt;/li&gt;    &lt;li&gt;&lt;font color="#800000"&gt;Be polite&lt;/font&gt;. &lt;strong&gt;Please&lt;/strong&gt; and &lt;strong&gt;Thank You &lt;/strong&gt;are magic words, whether you get the answer you were looking for or not. &lt;/li&gt; &lt;/ol&gt;  &lt;p&gt;I’ll add one thing when you’re responding to a blog – not just mine, anyone’s. If you want to ask a question, ask it as a reply to a post, not an e-mail. The author wants to answer the question once, and it’s almost a guarantee that you’re not the only one with that question. Also, other readers might know the exact answer and help you even more. I know, you have to register, all that stuff. Just consider it the price of getting your answer.&lt;/p&gt;&lt;img src="http://sqlblog.com/aggbug.aspx?PostID=21982" width="1" height="1"&gt;</description><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/Help/default.aspx">Help</category><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/Questions/default.aspx">Questions</category><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/Rant/default.aspx">Rant</category><category domain="http://sqlblog.com/blogs/buck_woody/archive/tags/SQL+Server/default.aspx">SQL Server</category></item></channel></rss>