Sqlservercentral,titles and points

  • karthik M

    One Orange Chip

    Points: 29139

    I want to know the name of all titles given by our sqlservercentrsl.com site. I mean, my title is 'SSC Addicted' like that how many titles are there ? Also i want to know the title name with the corresponding points.

    karthik

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 715064

    Forum Newbie 0

    Grasshopper 10

    SSC Rookie 25

    Valued Member 50

    SSC Journeyman 75

    SSC-Enthusiastic 100

    SSC Veteran 200

    Old Hand 300

    SSC-Addicted 400

    Mr or Mrs. 500 500

    SSChasing Mays 600

    Right there with Babe 714

    SSC Eights! 800

    Ten Centuries 1,000

    SSCommitted 1,500

    SSCrazy 2,000

    Hall of Fame 3,000

    SSCarpal Tunnel 4,000

    SSCertifiable 5,000

    SSCrazy Eights 8,000

    SSChampion 10,000

  • Steve Jones - SSC Editor

    SSC Guru

    Points: 715064

    Feel free to suggest other levels and/or names

  • quackhandle1975

    SSChampion

    Points: 10963

    2500 - The Buck Rogers Era

    Or to be more precise, 2419 (AD). 😉

    qh

    [font="Tahoma"]Who looks outside, dreams; who looks inside, awakes. – Carl Jung.[/font]
  • Dwain Camps

    SSC Guru

    Points: 86873

    Steve Jones - SSC Editor (11/26/2007)


    Feel free to suggest other levels and/or names

    Not suggesting a new level but apparently I've achieved "Default port," whatever that is (see attached). :hehe:


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • Gail Shaw

    SSC Guru

    Points: 1004424

    That's a very old list (2007 thread). Steve's added several since then.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • anthony.green

    SSC Guru

    Points: 112212

    I believe that this is the latest, unsure if Steve has added any more since this

    http://www.sqlservercentral.com/Forums/Topic935523-83-1.aspx



    How to post data/code for the best help - Jeff Moden[/url]
    Need a string splitter, try this - Jeff Moden[/url]
    How to post performance problems - Gail Shaw[/url]
    Managing Transaction Logs - Gail Shaw[/url]
    Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger[/url]

  • Dwain Camps

    SSC Guru

    Points: 86873

    anthony.green (10/1/2012)


    I believe that this is the latest, unsure if Steve has added any more since this

    http://www.sqlservercentral.com/Forums/Topic935523-83-1.aspx

    IC. Very odd breakpoint there at 1433 and even odder that I should notice it!


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

  • Gail Shaw

    SSC Guru

    Points: 1004424

    Err... 1433 being the default port for SQL Server and 1434 being the UDP broadcast port?

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Dwain Camps

    SSC Guru

    Points: 86873

    GilaMonster (10/1/2012)


    Err... 1433 being the default port for SQL Server and 1434 being the UDP broadcast port?

    Ahhh... enlightnment can be a scary thing.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St

Viewing 10 posts - 1 through 10 (of 10 total)

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