I really appreciate the time you have taken to help me with this problem.
I will be out of the office until around 1:00PM and will try your
suggestions.
I did attach a copy of the query but it may have been stripped somewhere
along the line so I have placed it in line below.
select *
from p
I've been poking around google looking for tutorials and/or quick start
guides on optimizing the mysql server. We just upgraded our DB server from 2
Gb of RAM to 16. But I don't know how to reconfigure mysql to take full
advantage of it. Although, just installing the RAM seems to have made a hug
Configuring and optimising a MySQL server is highly dependent on your usage
of it. The most important question for you now is probably: which storage
engines do you use? Based on that, you should start configuring MySQL to
assign memory to optimise the usage of each as good as possible.
Have fun!
> I've been poking around google looking for tutorials and/or quick start
> guides on optimizing the mysql server. We just upgraded our DB server from
> 2
> Gb of RAM to 16. But I don't know how to reconfigure mysql to take full
> advantage of it. Although, just installing the RAM seems to have
High Performance MySql "Optimization, Backups, Replication, and more"
2nd Edition . Got a problem, pick a chapter and read the solution.
This book is awesome, I'm confident you will find what you are looking
for :) .
On Thu, Mar 5, 2009 at 12:30 PM, Stephen Edberg wrote:
>
>> I've been poking aro
Ingo,
On Wed, Mar 4, 2009 at 8:49 AM, Ingo Weiss wrote:
> Hi all,
>
> I have a view that is joining two base tables. I can update through
> the view, but insert only through the base tables. Now I am having the
> problem that seems to boil down to the following: When I insert into
> the base tabl
> At 07:38 PM 2/25/2009, you wrote:
>
>> >
>> > not sure, though, feel free to report test results
>>
>>Results not good so far. I created a big load file by creating a list of
>>all the files on my server (using "find / -printf ...). and appending
>> that
>
> This bug was reported back in 2006 and
> Is there a way I can restore the concurrent select feature to a working
> state without having to shut down the server and rebuild the entire data
> base?
Usually when concurrent insert is not permitted, it's because there
are holes in the table that cause inserts to go somewhere other than
at t
