Database table for exchange rates

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;







up vote
2
down vote

favorite












I want to create a table in my database to store the exchange rates for currencies so I don't have to make an api call every time.



My table has the following structure:



from_currency
to_currency
rate


If I have 170 currencies the table will have 170 * 170 (~29.000) entries. This seems a bit much for me. Is this the normal way to store exchange rates?






database-design







share|improve this question







New contributor




sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    up vote
    2
    down vote

    favorite












    I want to create a table in my database to store the exchange rates for currencies so I don't have to make an api call every time.



    My table has the following structure:



    from_currency
    to_currency
    rate


    If I have 170 currencies the table will have 170 * 170 (~29.000) entries. This seems a bit much for me. Is this the normal way to store exchange rates?






    database-design







    share|improve this question







    New contributor




    sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.





















      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I want to create a table in my database to store the exchange rates for currencies so I don't have to make an api call every time.



      My table has the following structure:



      from_currency
      to_currency
      rate


      If I have 170 currencies the table will have 170 * 170 (~29.000) entries. This seems a bit much for me. Is this the normal way to store exchange rates?






      database-design







      share|improve this question







      New contributor




      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      I want to create a table in my database to store the exchange rates for currencies so I don't have to make an api call every time.



      My table has the following structure:



      from_currency
      to_currency
      rate


      If I have 170 currencies the table will have 170 * 170 (~29.000) entries. This seems a bit much for me. Is this the normal way to store exchange rates?






      database-design




      database-design






      share|improve this question







      New contributor




      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 5 hours ago









      sascha

      1133




      1133




      New contributor




      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      sascha is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          There isn't really anything wrong with that design, its almost exactly what our production fact table looks like so you aren't far off. 29,000 rows isn't that many these days.



          Here is the structure that we use in our master warehouse:



          CREATE TABLE Fact.ExchangeRates
          (
           TradingDate DATE NOT NULL, 
           SourceCurrency CHAR(3) NOT NULL,
           TargetCurrency CHAR(3) NOT NULL,
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );


          Then, we have a fact table in each of our client data warehouse's that is built from the master. The data warehouses are set to use a single base currency so we can eliminate the source currency:



          CREATE TABLE Fact.ExchangeRates
          (
           DateKey DATE NOT NULL REFERENCES Dimension."Date"(DateKey),
           CurrencyKey CHAR(3) NOT NULL REFERENCES Dimension.Currency(CurrencyKey),
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );





          share|improve this answer
















          • 1




            Thanks for the great answer.
            – sascha
            4 hours ago










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "182"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );






          sascha is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f221182%2fdatabase-table-for-exchange-rates%23new-answer', 'question_page');

          );

          Post as a guest

















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          2
          down vote



          accepted










          There isn't really anything wrong with that design, its almost exactly what our production fact table looks like so you aren't far off. 29,000 rows isn't that many these days.



          Here is the structure that we use in our master warehouse:



          CREATE TABLE Fact.ExchangeRates
          (
           TradingDate DATE NOT NULL, 
           SourceCurrency CHAR(3) NOT NULL,
           TargetCurrency CHAR(3) NOT NULL,
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );


          Then, we have a fact table in each of our client data warehouse's that is built from the master. The data warehouses are set to use a single base currency so we can eliminate the source currency:



          CREATE TABLE Fact.ExchangeRates
          (
           DateKey DATE NOT NULL REFERENCES Dimension."Date"(DateKey),
           CurrencyKey CHAR(3) NOT NULL REFERENCES Dimension.Currency(CurrencyKey),
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );





          share|improve this answer
















          • 1




            Thanks for the great answer.
            – sascha
            4 hours ago














          up vote
          2
          down vote



          accepted










          There isn't really anything wrong with that design, its almost exactly what our production fact table looks like so you aren't far off. 29,000 rows isn't that many these days.



          Here is the structure that we use in our master warehouse:



          CREATE TABLE Fact.ExchangeRates
          (
           TradingDate DATE NOT NULL, 
           SourceCurrency CHAR(3) NOT NULL,
           TargetCurrency CHAR(3) NOT NULL,
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );


          Then, we have a fact table in each of our client data warehouse's that is built from the master. The data warehouses are set to use a single base currency so we can eliminate the source currency:



          CREATE TABLE Fact.ExchangeRates
          (
           DateKey DATE NOT NULL REFERENCES Dimension."Date"(DateKey),
           CurrencyKey CHAR(3) NOT NULL REFERENCES Dimension.Currency(CurrencyKey),
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );





          share|improve this answer
















          • 1




            Thanks for the great answer.
            – sascha
            4 hours ago












          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          There isn't really anything wrong with that design, its almost exactly what our production fact table looks like so you aren't far off. 29,000 rows isn't that many these days.



          Here is the structure that we use in our master warehouse:



          CREATE TABLE Fact.ExchangeRates
          (
           TradingDate DATE NOT NULL, 
           SourceCurrency CHAR(3) NOT NULL,
           TargetCurrency CHAR(3) NOT NULL,
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );


          Then, we have a fact table in each of our client data warehouse's that is built from the master. The data warehouses are set to use a single base currency so we can eliminate the source currency:



          CREATE TABLE Fact.ExchangeRates
          (
           DateKey DATE NOT NULL REFERENCES Dimension."Date"(DateKey),
           CurrencyKey CHAR(3) NOT NULL REFERENCES Dimension.Currency(CurrencyKey),
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );





          share|improve this answer












          There isn't really anything wrong with that design, its almost exactly what our production fact table looks like so you aren't far off. 29,000 rows isn't that many these days.



          Here is the structure that we use in our master warehouse:



          CREATE TABLE Fact.ExchangeRates
          (
           TradingDate DATE NOT NULL, 
           SourceCurrency CHAR(3) NOT NULL,
           TargetCurrency CHAR(3) NOT NULL,
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );


          Then, we have a fact table in each of our client data warehouse's that is built from the master. The data warehouses are set to use a single base currency so we can eliminate the source currency:



          CREATE TABLE Fact.ExchangeRates
          (
           DateKey DATE NOT NULL REFERENCES Dimension."Date"(DateKey),
           CurrencyKey CHAR(3) NOT NULL REFERENCES Dimension.Currency(CurrencyKey),
           ClosingRate DECIMAL(9,2) NOT NULL,
           AverageRate DECIMAL(9,2) NOT NULL
          );






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 4 hours ago









          Mr.Brownstone

          8,50422041




          8,50422041







          • 1




            Thanks for the great answer.
            – sascha
            4 hours ago












          • 1




            Thanks for the great answer.
            – sascha
            4 hours ago







          1




          1




          Thanks for the great answer.
          – sascha
          4 hours ago




          Thanks for the great answer.
          – sascha
          4 hours ago










          sascha is a new contributor. Be nice, and check out our Code of Conduct.









           

          draft saved


          draft discarded


















          sascha is a new contributor. Be nice, and check out our Code of Conduct.












          sascha is a new contributor. Be nice, and check out our Code of Conduct.











          sascha is a new contributor. Be nice, and check out our Code of Conduct.













           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f221182%2fdatabase-table-for-exchange-rates%23new-answer', 'question_page');

          );

          Post as a guest
































































          Comments

          Post a Comment

          Popular posts from this blog

          List of Gilmore Girls characters

          Image
          The season three cast—(Back row): Lane, Michel, Paris, Emily, Richard, Sookie, Miss Patty, Kirk; Front row: Jess, Luke, Lorelai, Rory, Dean This is a list of characters for the comedy-drama television series Gilmore Girls . Contents 1 Main characters 1.1 Lorelai Gilmore 1.2 Rory Gilmore 1.3 Sookie St. James 1.4 Lane Kim 1.5 Michel Gerard 1.6 Luke Danes 1.7 Emily Gilmore 1.8 Richard Gilmore 1.9 Paris Geller 1.10 Dean Forester 1.11 Jess Mariano 1.12 Kirk Gleason 1.13 Jason Stiles 1.14 Logan Huntzberger 2 Major recurring characters 2.1 Christopher Hayden 2.2 Jackson Belleville 2.3 Mrs. Kim 2.4 Tristin DuGray 2.5 Max Medina 2.6 Taylor Doose 2.7 Dave Rygalski 2.8 Marty 3 Recurring characters 3.1 Stars Hollow 3.2 Chilton 3.3 Yale 3.4 Other 4 Notable guest stars 5 Unseen characters 6 Notes 7 References Main characters Actor Character Appearances Season 1 Season 2 Season 3 Season 4 Season 5 Season 6 Season 7 A Year in the Life Lauren Graham Lorelai Gilmore...
          Read more

          What does second last employer means? [closed]

          Image
          Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
          Read more

          One-line joke

          A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
          Read more