Tag Info

New answers tagged

0

Test the inner query to see how well it performs. If you are missing an index on the foreign key, performance may be very slow. The size of your result set can cause performance issues with inner joins. The inner join may need to be run once for each row in your result set. Not having enough memory can cause an issue as data may need to be re-read from ...


2

Try making a temp table with just the data you need and doing a join to that. For each self join do another temp table. I would start with one at a time and check the performance.


1

If you are using Windows, you need not worry about named pipes at all. Why ? Years ago, MySQL for Windows had distributed three(3) different executables: mysqld.exe mysqld-nt.exe mysqld-max-nt.exe The two executeables mysqld-nt.exe and mysqld-max-nt.exe used the named pipes protocol. This is briefly mentioned in Chapter 23 Section 23.2 Page 353 ...


1

This is something you set up when starting the mysqld daemon (or service on Windows). You should (don't have Windows running) be able to see your startup options using the Task Manager (or failing that, use Process Explorer from here).



Top 50 recent answers are included