SQLServerCentral Rules of Conduct

  • Can you "sticky" this to the SQLServerCentral home page (ie. "How to ask a question and what to do with the answer" section) and force newbies to do a read (wishful thinking on my part) of this and Sushila's (can't find here article, just now) similar fine article before they can ask a question or post an answer?  This is good stuff and thank you for taking the time to do it.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    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".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • I wish. Unfortunately, too often people don't read the sticky things. I have to admit that on other sites I've missed them as well and restorted to asking an question of a webmaster that I probably should have found myself.

    As it is, I think I'll rerun this one every quarter or so

  • Aye, but if you sticky it, we know where to find it if we find someone not following the rules of conduct and we can refer them to it.

     

    K. Brian Kelley
    @kbriankelley

  • Heh... on Brian's note, Steve... I'm thinking "get the glue".

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    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".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • Then again, in hindsight, it is an article... so we can always find it quickly.

     

    K. Brian Kelley
    @kbriankelley

  • "The exception being you can insult me if you really want to."

    lol..that's funny.

    It's a good joke, but in all seriousness you should censor anybody who insults you, too. Don't think you need special treatment because you run the place; a complete ban on being a jerk is totally fair.

    Signature is NULL

  • It should also be noted that comments about an article are also in the forum and should follow the same rules. I have seen many posts complaining about an article, some bordering on flames. All criticism should be constructive; so, if you don't have a better solution to offer then you should file your comments using Notepad as Steve recommended.

    [font="Tahoma"]Bryant E. Byrd, BSSE MCDBA MCAD[/font]
    Business Intelligence Administrator
    MSBI Administration Blog

  • Thanks for posting this. Based on comments received for two articles that I've written, I doubt that I'll be posting again anytime soon. To bad these "rules of the road" weren't delivered in a more timely fashion. As a consultant with almost 10 years experience, in both OLTP and OLAP databases, along with over 5 years teaching experience at a local community college, I believe that I have a few things or two to add to the user community. However, if we get more excited here on, for instance, how many milliseconds we can shave off of a query by using ROWCOUNT instead of TOP (as seems to be the case), I'd probably be best to just keep some of my neat, interesting, or unusual (in the least) things to myself.

    I've posted with the handle "Lee" on SQLmag.com for 7 years and have never been flamed, etc. as I was here. Maybe because that is a "pay" board, so to speak, I don't know...

    Anyway, Thanks.

    Lee Everest

  • Lee,

    I can understand the discouragement you feel due to some of the comments to your bitmasking article, but I hope you'll continue to participate in this community. SSC has been a great SQL Server community over the years but it isn't without its share of problems for a site with as many visitors and participants as it has. But there are a lot of very good folks here who care a great deal about helping others and giving back to the community. Your article did add value to the community for it spurred a very healthy discussion about several areas related to database design. And it was a well-written article; I was and still am looking forward to part 2.

     

    K. Brian Kelley
    @kbriankelley

  • Lee,

    I absolutely agree with Brian on this one... I'm still looking forward to part 2, as well.  Don't let the flamers deter you... think of it like an iceberg... you can only "see" <10% of the users... the rest never say a thing, good or bad.  Unfortunately, the flamers are the ones most likely to respond.  I know it's hard to do but ignore them.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    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".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • OK, I went and read through the comments in question, and I didn't see any flame war. Maybe people weren't as nice as they could be, but they seemed decent overall. Sure, I saw Joe Celko made some comments, and he is sometimes a little...um...adrupt. But anybody who's read these forums (or his books) would know about that already, and take it with a grain of salt.

    After all, he's earned it; SQL would be in a better place overall if more people listened to him. And how many times does the guy have to repeat himself? Mostly every time I ignore Celko's advice I get myself into trouble down the road. And certainly every time I find myself cursing the previous developer on a project, it's because they got "clever" and now I've got to figure out what the heck is going on. Bitwise searching certainly falls into the "clever" category, with all the good and bad that entails. So I as well am looking forward to the 2nd article, even if it's breaking the relational paradigm.

    One of these days I'm going to get around to writing an article, and then I guess I'll see if I can take my own advice.

    cl

    Signature is NULL

  • Ohhhh hold the phone right there... As much as I like Joe, his comments can really get out of hand... I don't care how good you are, no one has earned the right to bash people the way he does.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    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".

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

  • I for one, have seen Joe *bashing* all over the place and I do believe he deserve a bit of this article I don't care for how long he's been on this industry just put your self the the place of the target of his comments and you will definitely feel a very unpleasant sensation.

    Just my $0.02


    * Noel

  • I have read a few comments that seem a little 'strong' to me but I have to remind myself that this is an imperfect mode of communication and that one needs a little patience.  Some articles are more useful than others to be sure, but I tip my hat to everyone who takes a shot at writing for SSC and certainly appreciate feedback to when I have posted a problem.

    A sticky for the article is a good idea.

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply