Home Forums Database Design Design Ideas and Questions Problem (doubt) with an Index on a composite key RE: Problem (doubt) with an Index on a composite key

  • October 8, 2012 at 9:25 am

    #1546791

    Carl0s_ (10/8/2012)

    Can someone tell me an opinion about this design?, is bad to use composite key in that way, is better to use subrogate? and what is better way to perform this?

    Why do you need an 'entity' table to link your countries table and your cities table? Surely it introduces a complication. Your cities table could be like this:

    CityID CityName State_Region CountryID

    1 Dallas Texas 1 (USA)

    2 Dallas Morayshire 2 (Scotland)

    “Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

    For fast, accurate and documented assistance in answering your questions, please read this article.
    Understanding and using APPLY, (I) and (II) Paul White
    Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden