﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2005 / SQL Server 2005 Performance Tuning  / Join's and Index's / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Fri, 24 May 2013 04:27:32 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>Maybe the clustered index that re-arranged the pages created disk fragmentation?</description><pubDate>Wed, 17 Apr 2013 10:49:56 GMT</pubDate><dc:creator>mmartin1</dc:creator></item><item><title>RE: Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>Thanks for your help.. BTW I put a covering index into place, but the job that inserts data into that table grew from 30min to 90min (give or take a few min). So I have removed the covering index, and the run time is back down. While the difference in run time of this query is only about 2min. Given that this query only runs once per day.. I am going to leave the covering index off.</description><pubDate>Fri, 01 Feb 2013 08:09:28 GMT</pubDate><dc:creator>dwilliscp</dc:creator></item><item><title>RE: Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>You really should have both on a permanent table. Maybe as one and the same thing, maybe different.</description><pubDate>Thu, 31 Jan 2013 07:10:34 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>RE: Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>Thanks... BTW it is an inner join. I have already sent a request off to the software company to see if we can create a PK. Currently there is not one. I will see about a clustered index, if we can not get a PK put into place.</description><pubDate>Thu, 31 Jan 2013 07:04:26 GMT</pubDate><dc:creator>dwilliscp</dc:creator></item><item><title>RE: Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>Maybe. Maybe not. Depends on the rows involved, the join type, other filters, complexity of the query, data types and a few other things. Add indexes, see if they help.Temp tables are not necessarily memory resident, but anything that they query processor operates on will be in memory, temp or permanent, the query processor doesn't know what a disk is.Ignoring joins, the permanent table needs a clustered index.</description><pubDate>Wed, 30 Jan 2013 12:35:38 GMT</pubDate><dc:creator>GilaMonster</dc:creator></item><item><title>Join's and Index's</title><link>http://www.sqlservercentral.com/Forums/Topic1413740-360-1.aspx</link><description>I am fuzzy on this.. so looking to see if my thoughts are correct... When looking at the execution plan, it does not ask for an index, but...If you have two moderate (500K to 1M) tables, and both are a heap, wouldn't it help the inner join to have index's on what is being joined? If it matters, one is a temp table (#temp) so it would already exist in memory.. one would hope.</description><pubDate>Wed, 30 Jan 2013 12:22:54 GMT</pubDate><dc:creator>dwilliscp</dc:creator></item></channel></rss>