New to SQL Server 2008

  • Hi All,

    I have worked in SQL 2000 and 2005 environment till now.

    However my manager told me to take a new assignment in SQL server 2008.

    I hope it should not be much challanging to start with.

    However please guide me what are the areas I should start to look into.

    --rhythmk
    ------------------------------------------------------------------
    To post your question use below link

    https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
    🙂

  • Hi! Maybe, if you are familiar with 2005, it would be reasonable to start from here.

    What's New (SQL Server 2008)


    I am really sorry for my poor gramma. And I hope that value of my answers will outweigh the harm for your eyes.
    Blog: http://somewheresomehow.ru[/url]
    Twitter: @SomewereSomehow

  • From the T-SQL perspective IMHO, the MERGE statement, table value constructors (TVC) and grouping sets are probably what I'd consider the most interesting. Add to that maybe User-defined table types (for passing tables into SPs and FUNCTIONs) and spatial data if that's what floats your boat.

    Using TVC there is a cool new way to UNPIVOT: http://www.sqlservercentral.com/articles/CROSS+APPLY+VALUES+UNPIVOT/91234/

    [/shameless-plug]


    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

  • check out msdn for new additions in the 2008 ;the datatypes , filegroups , new keywords (MERGE,OUTPUT etc..)

    for 2005 to 2008 you are good to go , for 2000 to 2008 not sure..

    ~ demonfox
    ___________________________________________________________________
    Wondering what I would do next , when I am done with this one :ermm:

  • demonfox (8/17/2012)


    check out msdn for new additions in the 2008 ;the datatypes , filegroups , new keywords (MERGE,OUTPUT etc..)

    for 2005 to 2008 you are good to go , for 2000 to 2008 not sure..

    The OUTPUT clause is a SQL 2005 feature:

    http://msdn.microsoft.com/en-us/library/ms177564(v=sql.90).aspx


    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

  • Thanks to all for your valuable input 🙂

    --rhythmk
    ------------------------------------------------------------------
    To post your question use below link

    https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
    🙂

  • And don't forget spatial data. That's a huge bit of functionality introduced in 2008.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • dwain.c (8/17/2012)


    The OUTPUT clause is a SQL 2005 feature:

    http://msdn.microsoft.com/en-us/library/ms177564(v=sql.90).aspx

    thanks dwain for correcting ...

    ~ demonfox
    ___________________________________________________________________
    Wondering what I would do next , when I am done with this one :ermm:

Viewing 8 posts - 1 through 7 (of 7 total)

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