Re: Improving DSS join/sort performance.

With only 1500 rows it sounds like you should make sure you have index's to use, update statistics, and yes - the OPTCOMPIND value will make a difference. Try using SET EXPLAIN ON so you can see how it is actually going to do your join for hints as to where you can speed it up. Also, how much cache you are using and temp disk space performance will affect your results. I've seen on some under powered systems where the optimizer decided to use hash joins even with an index present. Changing OPTCOMPIND then made it run very fast. S.W. dmoeller@geocities.com wrote in message <6paj9i$br1$1@nnrp1.dejanews.com>... >Hello everyone, > >Looking for tips on increasing SQL performance when using a Data Warehouse and >a lot of joins... Just general suggestions, etc. I have a few queries that >are taking forever (an hour or more) that are doing joins where all 6 tables >involved have less than 1500 rows... This seems extreme to me for the amount >of data. I'm currently running them, changing things, running them again, >etc. But wondered if anyone out there has seen this before and has some >suggestions.... Opinions on OPTCOMPIND settings in relation to join >performance? In OLTP I have always set it to 0 but currently have it at 2 and >am about to test with 0,1 to see how that works with the DSS here.... > >Thanks, > >David Moeller. > >-----== Posted via Deja News, The Leader in Internet Discussion ==----- >http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum