Very nice, indeed! It's this type of attention to the forums that makes SQLServerCentral so great.
We all have to remember that a person asking a question has already swallowed a certain amount of pride... let's make their visit one to remember for the RIGHT reasons. A Mentor-like attitude on our part not only helps the person asking the question, it reaffirms our professionalism as database Architects, Developers, and Analysts to the user community in general.
I agree with Bryant Byrd's post above... there are a couple of things that people needing help can do to expedite a correct answer from the forum...
- To reiterate what Bryant suggested, put something pertinent in the subject line of the thread. When I'm in a hurry (most of the time), I tend to skip things like "Need help ASAP" or "SQL Question" in favor of those subjects that I know I have some expertise in.
- Format your code. SQLwritteninallonelineandalllowercaseisdifficulttoreadandunderstand.
- Limit the scope of your quesiton to 1 or 2 problems.
- Provide table details and some data. If you really want to help busy folks like me answer your more complex questions, post not only the code you need help with, but post some table creation and data insert statements and then explain the relationship between the tables you are trying to achieve. Remember that your original code may be the problem so don't rely soley upon it to explain what you are trying to do.
- If an error has occurred, always copy and paste the full error message as well as the offending snippet of code (do not include passwords, SSNs, or other sensitive information).
- Identify the version and edition of SQL Server you are using. It can make a significant difference!
I look forward to another full year of great questions, great answers, and helpful articles. Hat's off to Andy, Steve, and the rest of the folks at SQLServerCentral.com!
Database Architect/Data Analyst
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
"Change is inevitable... change for the better is not".
"If "pre-optimization" is the root of all evil, then what does the resulting no optimization lead to?"
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)