Post reply

Subqueries

  • November 10, 2013 at 2:46 pm

    #282242

    1. I need to find the names of the customers who have purchased academic books. (Coding required as Subquery NOT as Join)

    2. Here, I need to show a list of authors who have written books

    and list the books they have written.

    Sort the list by last name

    (Coding required as Subquery)

    Thanks in advance.

  • November 10, 2013 at 6:08 pm

    #1665358

    Any time I see something like "Coding required as Subquery NOT as Join" it tells me for sure this is homework.

    You'll find that few on this forum are willing to do your homework for you.

    However if you make a fair attempt at solving the problem, we're likely to try to help you get it right.

    Suggest you post some table DDL and sample test data in a consumable form, along with your first attempt.

    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

  • November 10, 2013 at 10:05 pm

    #1665363

    dwain.c (11/10/2013)

    Any time I see something like "Coding required as Subquery NOT as Join" it tells me for sure this is homework.

    You'll find that few on this forum are willing to do your homework for you.

    However if you make a fair attempt at solving the problem, we're likely to try to help you get it right.

    Suggest you post some table DDL and sample test data in a consumable form, along with your first attempt.

    +1 to all that. Well said on all fronts.

    --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)

  • November 11, 2013 at 9:51 pm

    #1665634

    May be he want to learn about sub-queries.

  • November 12, 2013 at 2:28 am

    #1665657

    T.Ashish (11/11/2013)

    May be he want to learn about sub-queries.

    Good point! In that case, I suggest to check here:

    http://beginner-sql-tutorial.com/sql-subquery.htm

    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 5 posts - 1 through 4 (of 4 total)

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