Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Need help doing a SQL JOIN of 2 tables using MySQL

Posted on 2013-05-26
2
Medium Priority
?
225 Views
Last Modified: 2013-05-27
I'm not a big SQL user and am having trouble with a join statement.
I have these two tables:

CREATE TABLE `daily_index_weightings` (
  `idindex_weightings` int(11) DEFAULT NULL,
  `Custom_Index_Name` varchar(75) NOT NULL,
  `symbol` varchar(9) NOT NULL,
  `trade_date` date NOT NULL,
  `mktcap_weighting` float DEFAULT NULL,
  `volprice_weighting` float DEFAULT NULL,
  `combo_weighting` float DEFAULT NULL,
  `idx_rank_for_date` float DEFAULT NULL,
  PRIMARY KEY (`Custom_Index_Name`,`symbol`,`trade_date`),
  UNIQUE KEY `idx_name_sym_date_key` (`Custom_Index_Name`,`symbol`,`trade_date`),
  KEY `idx_name_symbol` (`Custom_Index_Name`,`symbol`),
  KEY `TradeDate` (`trade_date`)
) 

Open in new window


And:
CREATE TABLE `full_daily_data` (
  `Symbol` varchar(9) NOT NULL,
  `Trade_Date` date NOT NULL DEFAULT '0000-00-00',
  `Day_Open` float DEFAULT NULL,
  `Day_High` float DEFAULT NULL,
  `Day_Low` float DEFAULT NULL,
  `Day_Close` float DEFAULT NULL,
  PRIMARY KEY (`Symbol`,`Trade_Date`),
  KEY `TradeDate` (`Trade_Date`)
);

Open in new window


The results I'm trying to get are rows:
full_daily_data.Trade_Date
full_daily_data.Day_Open
full_daily_data.Day_Close
full_daily_data.symbol
daily_index_weightings.idx_rank_for_date
where daily_index_weightings.Custom_Index_Name = 'Oil Stocks'
where daily_index_weightings.Trade_Date = full_daily_data.trade_date
where daily_index_weightings.symbol = full_daily_data.symbol
where Trade_Date >= '2010/01/01' and Trade_Date <= '2012/01/31'

This is what I have now:
SELECT 
full_daily_data.Trade_Date, 
full_daily_data.Day_Open, 
full_daily_data.Day_Close, 
full_daily_data.Symbol, 
daily_index_weightings.idx_rank_for_date
FROM full_daily_data
INNER JOIN daily_index_weightings ON daily_index_weightings.Symbol = full_daily_data_1.Symbol 
AND daily_index_weightings.Trade_Date = full_daily_data.Trade_Date
WHERE full_daily_data.trade_date >= '2010/01/01' AND full_daily_data.trade_date <= '2012/12/31' 
AND daily_index_weightings.custom_index_name = 'Oil-and-Gas-Driller-Explorer-Stocks'
ORDER BY full_daily_data.trade_date, daily_index_weightings.idx_rank_for_date;

Open in new window


It works, but I'm only using it on a small sample set so far.  The amount of data I plan to use it on is HUGE.

Is this the best/most efficient way to use it?  I'm not opposed to using or adding indices if that will help fetch time (insert time is not a big issue).
WHY does it work?  I'm not really sure, a lot of it was guessing and I was shocked that it did actually work.  Does it matter if the date for my where clause comes from one table vs. the other?

Any help with these questions would be appreciated!
0
Comment
Question by:cashonly
2 Comments
 
LVL 49

Accepted Solution

by:
PortletPaul earned 2000 total points
ID: 39198266
Looks fine to me, you have joined the 2 tables using a primary key:
(PRIMARY KEY (`Symbol`,`Trade_Date`)

I don't know the data, but as you are using an inner join this means there HAS to be a match between the 2 tables. This is a good join type to use so don't change it unless there is a need (and such a need would only arise if you can have a record in one of those tables that does not exist in the other table).

I would suggest a small change to you date range filtering, instead of less than and equal on the upper date boundary, use less than and move that date up 1 day, like this:

WHERE full_daily_data.trade_date >= '2010-01-01'
      AND full_daily_data.trade_date < '2013-01-01' --<< one day up from '2012/12/31'
      AND daily_index_weightings.custom_index_name = 'Oil-and-Gas-Driller-Explorer-Stocks'

>>Does it matter if the date for my where clause comes from one table vs. the other?
in this case no as those dates are part of the inner join it would not really make any diffrence

If the data is HUGE, then you may want to compare execution plans of some alternatives:
/* alt 1 */
SELECT full_daily_data.Trade_Date
	, full_daily_data.Day_Open
	, full_daily_data.Day_Close
	, full_daily_data.Symbol
	, daily_index_weightings.idx_rank_for_date
FROM full_daily_data
INNER JOIN daily_index_weightings
	ON daily_index_weightings.Symbol = full_daily_data_1.Symbol
		AND daily_index_weightings.Trade_Date = full_daily_data.Trade_Date
		AND daily_index_weightings.custom_index_name = 'Oil-and-Gas-Driller-Explorer-Stocks'
WHERE full_daily_data.trade_date >= '2010-01-01'
	AND full_daily_data.trade_date < '2013-01-01' -- << one day up from '2012/12/31'
ORDER BY full_daily_data.trade_date
	, daily_index_weightings.idx_rank_for_date;

/* alt 2 */    
SELECT full_daily_data.Trade_Date
	, full_daily_data.Day_Open
	, full_daily_data.Day_Close
	, full_daily_data.Symbol
	, daily_index_weightings.idx_rank_for_date
FROM daily_index_weightings
INNER JOIN full_daily_data
	ON daily_index_weightings.Symbol = full_daily_data_1.Symbol
		AND daily_index_weightings.Trade_Date = full_daily_data.Trade_Date
WHERE daily_index_weightings.custom_index_name = 'Oil-and-Gas-Driller-Explorer-Stocks'
	AND daily_index_weightings.Trade_Date >= '2010-01-01'
	AND daily_index_weightings.Trade_Date < '2013-01-01' -- << one day up from '2012/12/31'
ORDER BY full_daily_data.trade_date
	, daily_index_weightings.idx_rank_for_date;

Open in new window

0
 

Author Closing Comment

by:cashonly
ID: 39199078
Awesome stuff PortletPaul!

Just the kind of answer I was looking for!

I will use your code and run some tests when I get more data loaded in my DB.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When table data gets too large to manage or queries take too long to execute the solution is often to buy bigger hardware or assign more CPUs and memory resources to the machine to solve the problem. However, the best, cheapest and most effective so…
An alternative to the "For XML" way of pivoting and concatenating result sets into strings, and an easy introduction to "common table expressions" (CTEs). Being someone who is always looking for alternatives to "work your data", I came across this …
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

971 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question