<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0"
 xmlns:blogChannel="http://backend.userland.com/blogChannelModule"
 xmlns:atom="http://www.w3.org/2005/Atom"
>

<channel>
<title>Web Hosting Help Resources tagged query</title>
<link>http://www.Bluehost.com/hosting/help/tag/query</link>
<description>Web Hosting Help Resources tagged query</description>
<language>en-us</language>
<copyright>Copyright 2010, Bluehost.com</copyright>
<lastBuildDate>Tue, 06 Dec 2016 10:34:49 MDT</lastBuildDate>

<item>
<title>CPU Performance Issues</title>
<link>http://www.Bluehost.com/hosting/help/resource/564</link>
<description>What is CPU Protection</description>
<category>cpu</category>
<category>database</category>
<category>mysql</category>
<category>optimize</category>
<category>peak</category>
<category>performance</category>
<category>query</category>
<category>script</category>
<category>slow</category>
<guid isPermaLink="false">http://www.Bluehost.com/hosting/help/resource/564</guid>
<pubDate>Tue, 06 Dec 2016 10:34:49 MDT</pubDate>
</item>
<item>
<title>Optimizing MySQL: Queries and Indexes Article 4 of 4</title>
<link>http://www.Bluehost.com/hosting/help/resource/438</link>
<description>Optimizing MySQL: Queries and Indexes Article 4 of 4 Courtesy of:Ian Gilfillan Most systems need to be highly optimized for selects - take a news site which performs millions of queries per day, but w</description>
<category>cpu</category>
<category>exceeded</category>
<category>index</category>
<category>indexes</category>
<category>mysql</category>
<category>optimize</category>
<category>optimizing</category>
<category>queries</category>
<category>query</category>
<guid isPermaLink="false">http://www.Bluehost.com/hosting/help/resource/438</guid>
<pubDate>Thu, 13 Oct 2016 02:25:23 MDT</pubDate>
</item>
<item>
<title>Optimizing MySQL: Queries and Indexes Article 3 of 4</title>
<link>http://www.Bluehost.com/hosting/help/resource/437</link>
<description>Optimizing MySQL: Queries and Indexes Article 3 of 4 Courtesy of: Ian Gilfillan Ordering by surname is a common requirement, so it would make sense to create an index on surname. But in this example o</description>
<category>cpu</category>
<category>exceeded</category>
<category>index</category>
<category>indexes</category>
<category>mysql</category>
<category>optimize</category>
<category>optimizing</category>
<category>queries</category>
<category>query</category>
<guid isPermaLink="false">http://www.Bluehost.com/hosting/help/resource/437</guid>
<pubDate>Thu, 13 Oct 2016 02:24:43 MDT</pubDate>
</item>
<item>
<title>Optimizing MySQL: Queries and Indexes Article 1 of 4</title>
<link>http://www.Bluehost.com/hosting/help/resource/435</link>
<description>Optimizing MySQL: Queries and Indexes Article 1 of 4 Courtesy of: Ian Gilfillan Badly defined or non-existent indexes are one of the primary reasons for poor performance, understanding and then fixing</description>
<category>indexes</category>
<category>mysql</category>
<category>optimize</category>
<category>optimizing</category>
<category>queries</category>
<category>query</category>
<guid isPermaLink="false">http://www.Bluehost.com/hosting/help/resource/435</guid>
<pubDate>Thu, 13 Oct 2016 02:22:26 MDT</pubDate>
</item>
<item>
<title>Optimizing MySQL: Queries and Indexes Article 2 of 4</title>
<link>http://www.Bluehost.com/hosting/help/resource/436</link>
<description>Optimizing MySQL: Queries and Indexes Article 2 of 4 Courtesy of: Ian Gilfillan Some knowledge of how indexes work allows you to use them more efficiently. Firstly, note that when you update a table w</description>
<category>indexes</category>
<category>mysql</category>
<category>optimize</category>
<category>optimizing</category>
<category>queries</category>
<category>query</category>
<guid isPermaLink="false">http://www.Bluehost.com/hosting/help/resource/436</guid>
<pubDate>Thu, 13 Oct 2016 02:24:12 MDT</pubDate>
</item>
</channel>
</rss>