<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: tips for MySQL newbies</title>
	<atom:link href="http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/feed/" rel="self" type="application/rss+xml" />
	<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/</link>
	<description>yet another MySQL DBA blog</description>
	<lastBuildDate>Thu, 10 Sep 2009 22:56:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-66</link>
		<dc:creator>John</dc:creator>
		<pubDate>Tue, 02 Oct 2007 14:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-66</guid>
		<description>Very helpful.  Will give me a head start before I take the jump.</description>
		<content:encoded><![CDATA[<p>Very helpful.  Will give me a head start before I take the jump.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-64</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Sat, 29 Sep 2007 22:24:11 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-64</guid>
		<description>MOving from a simple Access/Jet based system to a grown up MYSQL database backend supporting a numberof front end programs used in the manufacturing industry, I have found a number of issues not previoiusly considered, that I should be analysing and researching.  I imagine your comments will have saved me days in the long run, and cost me weeks in the learning process! ;)

Many thanks</description>
		<content:encoded><![CDATA[<p>MOving from a simple Access/Jet based system to a grown up MYSQL database backend supporting a numberof front end programs used in the manufacturing industry, I have found a number of issues not previoiusly considered, that I should be analysing and researching.  I imagine your comments will have saved me days in the long run, and cost me weeks in the learning process! <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Many thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diamond Notes &#187; Log Buffer #64: a carnival of the Vanities for DBAs</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-62</link>
		<dc:creator>Diamond Notes &#187; Log Buffer #64: a carnival of the Vanities for DBAs</dc:creator>
		<pubDate>Fri, 28 Sep 2007 16:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-62</guid>
		<description>[...] experienced Oracle DBA who is transitioning to MySQL blogs about his nine tips for new MySQL DBAs. They are quite enlightening. Along with that, the new DBA should take a look at [...]</description>
		<content:encoded><![CDATA[<p>[...] experienced Oracle DBA who is transitioning to MySQL blogs about his nine tips for new MySQL DBAs. They are quite enlightening. Along with that, the new DBA should take a look at [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Busse</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-61</link>
		<dc:creator>Dave Busse</dc:creator>
		<pubDate>Fri, 28 Sep 2007 11:18:31 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-61</guid>
		<description>George - Very helpful.  What tutorial (book, whitepaper, blog, etc) would you recommend for the MySQL newbie.  I&#039;m thinking in terms of a college student here.

Dave</description>
		<content:encoded><![CDATA[<p>George &#8211; Very helpful.  What tutorial (book, whitepaper, blog, etc) would you recommend for the MySQL newbie.  I&#8217;m thinking in terms of a college student here.</p>
<p>Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ben</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-56</link>
		<dc:creator>ben</dc:creator>
		<pubDate>Wed, 26 Sep 2007 19:10:54 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-56</guid>
		<description>George - agreed!  Thanks for your advice!

Ben</description>
		<content:encoded><![CDATA[<p>George &#8211; agreed!  Thanks for your advice!</p>
<p>Ben</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Trujillo</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-55</link>
		<dc:creator>George Trujillo</dc:creator>
		<pubDate>Wed, 26 Sep 2007 19:04:40 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-55</guid>
		<description>I think it is very important that DBAs (especially new ones) do sufficient planning, physical design, risk analysis and backup/recovery planning before installing MySQL.   MySQL is an easy database to install and configure on a wide range of platforms.

However if sufficient planning is not performed up front, a DBA is going to have problems as their databases grows, issues come up and more users start accessing the system.  A top 10 list of things to do before installing a MySQL database include:
1) Understand the purpose and potential growth of your database.
2) Determine the appropriate physical layout of your database.  The defaults are not always the best long term layout.
3) Select the appropiate storage engines and how they impact performance and your backup/recovery strategies.
4) Layout your backup and recovery strategy.  Pick the appropriate backup/recovery tools for your environment.  Then test your backup and recovery strategies sufficiently.
5) Understand the number of databases that will be created and the maintenance ramifications of the database layout.
6) What are the business costs and ramifications of this environment being down?  Perform appropriate risk analysis.
7) Understand how security is being managed and maintained for your users and your databases.
8) Set the appropiate SQL_MODE and make sure you understand the ramifications of the SQL_MODE selection.
9) Understand your physical storage layout. On your using separate disks, storage arrays, etc.
10) Define a set of best practices that determine your physical layouts, naming conventions, management tools, infrastructure management and document everything.

The five P&#039;s apply to database configurations.  Proper Planning Prevents Pitiful Performance.

George Trujillo</description>
		<content:encoded><![CDATA[<p>I think it is very important that DBAs (especially new ones) do sufficient planning, physical design, risk analysis and backup/recovery planning before installing MySQL.   MySQL is an easy database to install and configure on a wide range of platforms.</p>
<p>However if sufficient planning is not performed up front, a DBA is going to have problems as their databases grows, issues come up and more users start accessing the system.  A top 10 list of things to do before installing a MySQL database include:<br />
1) Understand the purpose and potential growth of your database.<br />
2) Determine the appropriate physical layout of your database.  The defaults are not always the best long term layout.<br />
3) Select the appropiate storage engines and how they impact performance and your backup/recovery strategies.<br />
4) Layout your backup and recovery strategy.  Pick the appropriate backup/recovery tools for your environment.  Then test your backup and recovery strategies sufficiently.<br />
5) Understand the number of databases that will be created and the maintenance ramifications of the database layout.<br />
6) What are the business costs and ramifications of this environment being down?  Perform appropriate risk analysis.<br />
7) Understand how security is being managed and maintained for your users and your databases.<br />
 <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_cool.gif' alt='8)' class='wp-smiley' /> Set the appropiate SQL_MODE and make sure you understand the ramifications of the SQL_MODE selection.<br />
9) Understand your physical storage layout. On your using separate disks, storage arrays, etc.<br />
10) Define a set of best practices that determine your physical layouts, naming conventions, management tools, infrastructure management and document everything.</p>
<p>The five P&#8217;s apply to database configurations.  Proper Planning Prevents Pitiful Performance.</p>
<p>George Trujillo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Useful tips for MySQL newbies &#171; François Schiettecatte&#8217;s Blog</title>
		<link>http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-54</link>
		<dc:creator>Useful tips for MySQL newbies &#171; François Schiettecatte&#8217;s Blog</dc:creator>
		<pubDate>Wed, 26 Sep 2007 11:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://oracle2mysql.wordpress.com/2007/09/25/tips-for-mysql-newbies/#comment-54</guid>
		<description>[...] Useful tips for MySQL&#160;newbies  Some useful tips for MySQL newbies. [...]</description>
		<content:encoded><![CDATA[<p>[...] Useful tips for MySQL&nbsp;newbies  Some useful tips for MySQL newbies. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
