At this year’s MySQL Conference & Expo, taking place in Santa Clara, California in mid-April, I’m giving two sessions: Best Practices for Database Administrators,Database Security Using White-Hat Google Hacking. You can see more info about me here, including descriptions of the workshops.
I would not wish this task on my worst enemy. My friend, good luck and best wishes but I’m afraid I just can’t help you, because that much suffering is way too much for me.
Here’s another question that came to me about 2 weeks ago from a user group member that I never had time to research and answer. I have directed the original author to this post so questions you pose in the comments can be answered.
I was asked this question in an e-mail — feel free to ask your questions in the comments, as I will point the original author to this post to answer those questions. There is not a lot of data here, so instead of me asking questions in an e-mail I figured I would open it up to the (MySQL) world. Without further ado, here’s the question…
I wrote this post because I feel there is a great need for it. The number of people struggling with unstable query plans due to bind peeking in Oracle 10G is enormous, to say the least. More than that, solutions like disabling bind variable peeking are driving us away from understanding the root cause of the problem and applying the right fix to it.
RDA 4.11 is out, with a couple of new features. “Oracle Database Diagnostics Collector” (ORADDC) is one of those. It allows you to easily activate all kinds of traces, dumps, or stack collections. This may become one of the most used RDA modules for Oracle Support Services and Oracle database administrators stuck in different situations. For now, let’s start with a more basic question: “How to leverage RDA in a RAC environment ?”
We’ve been running into a problem with one client: SELECT COUNT(*) FROM tbl; takes 0.25 seconds on one db, and 0.06 seconds on another.
Consistently. That’s a fourfold difference. There aren’t any significant configuration differences (like query cache, etc.), the software versions are the same, and the table fits into memory. This has been looked at by at least 3 in-house MySQL experts, and the only thing we can determine is that it’s a hardware difference.
I have created a MySQL Professionals Group for networking with others in the space, in the tradition of the Oracle Professionals group and the SQL Server Professionals groups that I already participate in. This is a great way to network with other professionals in your field of work. I hope you join us.
Are you interested in attending the 2008 MySQL Conference & Expo? I’m happy to announce that LinuxQuestions.org is able to give away one pass to the event. Visit this link for additional information. Good luck.
As of this month, Adam Machanic has been hired to lead Pythian’s global SQL Server practice and will be working out of our office in Central Square in Boston, Massachussets. Adam is in my opinion as close as it comes to a resource in the Microsoft SQL Server space that has the personality, track record and respect that Tom Kyte has in the Oracle space.