|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
I have a MySQL database with 25 tables running on Apache. One of my tables (shopper table) has close to 300,000 records and I use this table quit frequently for queries. I came across a problem using a query to access my shopper table and another table (this table has around 15,000 records) to pull the necessary information. The problem is that when I run this query it runs for a long period of time then the database crashes (with no query result). Can MySQL handle only a certain amount of records before it becomes overburdened? Also, I am using PHP 3 to run this query. Thanks.
|
|
#2
|
|||
|
|||
|
"I came across a problem using a query to access my shopper table and another table (this table has around 15,000 records)..."
Can we assume you are joining the two tables? How are you joining them (post your query). If you aren't doing the join right you'll end up with a temp table of 45G records! |
|
#3
|
||||
|
||||
|
Exactly how many is 45G?
|
|
#4
|
|||
|
|||
|
45,000,000,000
|
|
#5
|
|||
|
|||
|
Yeah, with big tables like that a bad JOIN can be a major problem... And use EXPLAIN to make sure you have your indexes set up right...
|
![]() |
| Viewing: Dev Shed Forums > Databases > MySQL Help > Crashing MySQL |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|