Re: HPL and PDQ

"Tisha" <loden@networkip.net> wrote in message news:8085cdee.0408240701.35b83299@posting.google.com... > Neil, > > Did you get this to work with onpload in 9.4? I have used HPL alot in > past releases and never gotten it to use the pdq settings for an index > build. My work around has always been to build the table with no > indexes, load the data using hpl, and then build the indexes in a > seperate sql setting pdqpriority and isolation level there. I am > getting ready to move to 9.4 soon and I would be interested in > learning more about how this works in the newer release. I have > several large tables I have to rebuild occasionally and getting this > to work directly in hpl would be a huge help. I raised a call with UK Tech Support. Call 411407 refers. Here's what they said: "I believe that there is no mechanism for HPL to pick up the PDQ environment variables from the engine. Enabling PDQ on the database engine environment may give the desired results, however this will mean that all of your sessions will use PDQ. This problem is not necessarily a bug, but more like a feature request. Therefore, I have logged the following feature request for this problem: Feature - 169414 HPL ONPLOAD JOB TAKES LONGER TO ENABLE INDEXES THAN SQL ENABLE INDEX" This didn't in fact *quite* answer the question I'd asked, but the follow did: that there is no way to get onpladm to pass the PDQ thingies on. So for the time being the workaround is to cancel the load once all the rows are in and enable the indexes in a separate SQL run with the PDQ variables set.