Admin Linux ... MySQL DBA

Security Issues with MySQL ROOT Access MySQL offers simple but very effective security mechanisms. Unfortunately, the default installation of MySQL, and in particular the empty root password and the potential vulnerability to buffer overflow attacks, makes the database an easy target for attacks. In order to achieve the highest possible level of security, the installation and configuration of MySQL should be performed in accordance with the following security requirements: * MySQL processes must run under a unique UID/GID that is not used by any other system process. * Only local access to MySQL need to be allowed.(some exceptions for jobs/backups) * MySQL root's account must be protected by a complex/hard to guess password. * The administrator's account (root) need to be renamed. * Anonymous access to the database (by using the nobody account) must be disabled. MySQL Security risks can be categorized into the following. * Filesystem security risks. MySQL Install

MySQL Development History - MySQL was first released internally on 23 May 1995 - Windows version was released on January 8, 1998 for Windows 95 and NT - Version 3.23: beta from June 2000, production release January 2001 - Version 4.0: beta from August 2002, production release March 2003 - Version 4.1: beta from June 2004, production release October 2004 - Version 5.0: beta from March 2005, production release October 2005 - Version 5.1: currently pre-production (since November 2005) - Sun Microsystems acquires MySQL AB on 26 February 2008 MySQL Features History - Version 3.23.23 Full-Text Search - Version 4.0 Full-Text Search (IN BOOLEAN MODE), UNIONS - Version 4.1 R-Tree and B-Tree, Sub-Queries, Prepared Statements - Version 5.0 Cursors, Stored Procedures, Triggers, Views, XA Transactions - Version 5.1 Event Scheduler, Partitioning, Plugin API, Row-Based Replication, Server Log Tables

In Unix/Linux world everything is treated as files. whether it is a devices, directories and sockets — all of these are files. Stat command displays file or file system status. [Prabhat@Server1 Archive]$ stat 1_16470_587807474.arc File: `1_16470_587807474.arc' Size: 208514560 Blocks: 407664 IO Block: 4096 regular file Device: fd02h/64770d Inode: 17006596 Links: 1 Access: (0640/-rw-r-----) Uid: ( 500/ oracle) Gid: ( 500/ dba) Access: 2010-06-12 23:28:58.000000000 -0700 Modify: 2010-06-12 23:31:22.000000000 -0700 Change: 2010-06-12 23:31:22.000000000 -0700 Details of Linux Stat Command Output * File: `1_16470_587807474.arc’ – Name of the file. * Size: 208514560 – File size in bytes. * Blocks : 407664 – Total number of blocks used by this file. * IO Block : 4096 – IO block size for this file. * regular file – Indicates the file type. This indicates that this is a regular file. Following are available file types. o regular file. ( ex: all normal fi

Limit is used to limit your MySQL query results to those that fall within a specified range. You can use it to show the first X number of results, or to show a range from X - Y results. It is phrased as Limit X, Y and included at the end of your query. X is the starting point (remember the first record is 0) and Y is the duration (how many records to display). Table 'example' have following data. SELECT * FROM `example` ORDER BY `example`.`age` ASC LIMIT 0 , 30 id name age 3 Amit 26 5 pani 27 2 Sanjay 28 4 Lucky 29 6 atul 30 1 Kumar 31 SELECT * FROM `example` ORDER BY `example`.`age` ASC LIMIT 3 , 1 id name age 4 Lucky 29 This will show records 3rd only ( remember the first record is 0 )