It's always the little things in life. One of the things that has been a very "little thing" that causes a lot of frustration while writing The MySQL Administrator's Bible is the prompt. Specifically, the fact that you can only change the first line of the prompt, but not the subsequent lines.

There's no video for Jacob Nikom's December 2007 Boston MySQL User Group meeting, but the slides for "Measuring MySQL Server Performance" can be downloaded (2.33 MB) at http://technocation.org/files/doc/Measuring_MySQL_server_performance_03.pptAnd with that, this is (I believe) post #10,000 at Planet MySQL!

I was recently asked a question by someone who had attended my Shmoocon talk entitled "Why are Databases So Hard to Secure?". PDF slides are available (1.34 Mb). I was going to put this into a more formal structure, but the conversational nature works really well. I would love to see comments reflecting others' thoughts.I found several things of interest in your talk about database security and several new things to think about.In particular I realized that DBMSs have at least two hats in the world of software architecture namely as technical services ("smart file system") and as application framework. Perhaps that "depth" is one of the reasons why dbms is hard to secure? For example, considering just the question of who or what have user roles within a DBMS deployment. From the "deep" point of view, the "user" could be an application, or a module, or just the next layer up  []

Slides:http://www.technocation.org/files/doc/2009Keynote.pdfReferences:I am @sheeri on twitterMy blog is at http://pythian.com/blogs/author/sheeriMy e-mail is cabral@pythian.comPythian became the first ever Sun Enterprise Remote DBA Partner -- read the details at http://tinyurl.com/pythiansun.

Here are the slides and links I am using for the "Database Security Using White-Hat Google Hacking" at the 2008 MySQL Users Conference and Expo.pdf slidesWhere to Start:http://johnny.ihackstuff.com/ghdb.phpi-hacked.com/content/view/23/42

Slaves can be used for:Horizontal read scalability -- take the load off a master database by spreading reads to a replicated slave.Disaster recovery -- some disasters, such as a hardware failure, can be solved by having a slave ready to propagate to a master. This technique also works to make offline changes to a master/slave pair without having database downtime (see below).Consistent Backups -- without disrupting production usage, a slave can be used to ta

The "sla" in mysqlsla stands for "statement log analyzer". This does a much better job than mysqldumpslow of analyzing your slow query log. In fact, you can sort by many different parameters -- by sheer number of times the query shows up in the slow query log, by the total or average query time, by the lock time, etc. This is really good for weeding out pesky entries in the slow query log that you do not care about. In this case, our client was using log-queries-not-using-indexes, so there was a lot of junk in the slow query log as well (for instance, every time a mysqldump backup was run, the slow query log got plenty of entries). In this case, I'm using --slow to read the slow query log at the filename specified, --flat to flatten all the text to lowercase (basically case-insensitive matching) and --sort at to sort by "average time".> ./mysqlsla --flat --slow ~mysql/var/mysql-slow.log  []