Manners

SQLServerCentral is supported by Red Gate Software Ltd.

Home Tags Articles Editorials Forums Scripts Videos Blogs QotD Books Ask SSC SQL Jobs Training Authors About us Contact us Newsletters Advertise Write for us

Popular Topics

Home

Members

Calendar

Who's On

Home » SQLServerCentral.com » Editorials » Manners

65 posts, Page 7 of 7

«««3 4 5 6 7

Manners

Rate Topic

Display Mode

Topic Options

Author

Message

Jeff Moden

Posted Monday, April 13, 2009 9:31 PM

SSChampion

Group: General Forum Members
Last Login: Today @ 9:01 PM
Points: 20,164, Visits: 13,702

Lynn Pettis (4/13/2009)

In my blog, th flip side, I mention that the post should be concise yet detaled. Sort of an oxymoron, but it works.. The code should be well formatted with appropriate white space. The sample data readily consumbable without reformatting. The sample data easily comparable to the output.

You only need enough of an explaination so that people can understand the problem. They don't need all the details of the system, nor necessarily all the data from the tables, either in rows or columns. Just what is needed to understand and assist in solving the problem.

Sorry I missed it... what's the link for that, Lynn?

--Jeff Moden

"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

"Data isn't the only thing that's supposed to have Integrity."

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."

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #696289

Lynn Pettis

Posted Monday, April 13, 2009 9:58 PM

SSChampion

Group: General Forum Members
Last Login: Today @ 9:55 PM
Points: 11,934, Visits: 12,044

Here is the link http://www.sqlservercentral.com/blogs/lynnpettis/archive/2009/04/05/dealing-with-difficult-forum-users-the-flip-side.aspx#comments.

Cool

Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)

Post #696292

Jack Corbett

Posted Tuesday, April 14, 2009 2:15 AM

SSCrazy Eights

Group: General Forum Members
Last Login: Today @ 10:56 AM
Points: 8,186, Visits: 7,969

JJ,

The length of a post is not why I would skip one. It is the coherence and readability of a post that matters to me. I'll scroll through a long post if it is coherent and has some white space. If I have scroll through a hundred lines of code that is not in a code block, contains no white space, and no other formatting, I'll skip it and move on to the next question.

Jack Corbett

Applications Developer

Don't let the good be the enemy of the best. -- Paul Fleming

Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
How to Post Performance Problems
Crosstabs and Pivots or How to turn rows into columns Part 1
Crosstabs and Pivots or How to turn rows into columns Part 2

Post #696355

peter-757102

Posted Tuesday, April 14, 2009 2:20 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 4:26 AM
Points: 128, Visits: 929

You can problably psychologically trick a potential reader into feeling the post is short.
There are two ways.

Add the test code and the solutions you already tried as sql scripts

This doesnt take much place and it also allows you to add some detailed comments there without blowing a reader off in your main post.

Split tekst of the post itself in two parts

Describe in the first post the problem, end with a note that details follow in following posts. Have these following posts ready as you want people to read them as one if they are interested in it.

This first post if recognised by someone as something he or she knows a lot about serves just that. Catch their attention and also invoke anyone with a similar problem. Once that happends, reading more is not an issue as it is part of solving the problem.

Post #696359

JJ B

Posted Tuesday, April 14, 2009 8:40 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 10:09 AM
Points: 194, Visits: 1,626

I like to see the question up front and the explanation about the question second.

Grant: I like this too. I don't know that most posters are sophisticated enough to think about this, but it is another tip that could be added for people learning to post.

I'll scroll through a long post if it is coherent and has some white space.

Jack: Cool. That's more patience than I have.

Split text of the post itself in two parts.

peter: I've started doing this myself in other contexts. I also believe it helps and is another tip that could be shared. But this one is dangerous to share with people I think because it could cause people to post a lot of little posts unnecessarily.

Thanks all for weighing in. I was curious what you would say.

Post #696602

« Prev Topic | Next Topic »

65 posts, Page 7 of 7

«««3 4 5 6 7

Permissions