Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread time taken for sql with joins
Tue, Dec 11 2007 6:32 AMPermanent Link

L. Duncan
Hi
When I run the following SQL in ElevateDB it takes a long time to execute. The same SQL in DBISAM, however, executes almost immediately. I
wonder why this is the case?

SELECT a.AssetName, a.AssetCode FROM Assets a
LEFT OUTER JOIN ProductMappings m ON a.AssetCode=m.AssetCode
WHERE AssetManagerCode = 2759
AND +m.ProductCode = 13
ORDER BY AssetName

thanks
Tue, Dec 11 2007 7:27 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Probably lacking an index. Can you post the query plans for both DBISAM and ElevateDB?

Roy Lambert
Tue, Dec 11 2007 8:10 AMPermanent Link

L. Duncan
Roy Lambert <roy.lambert@skynet.co.uk> wrote:

Probably lacking an index. Can you post the query plans for both DBISAM and ElevateDB?

Roy Lambert

Hi Roy
Thanks for the quick reply. I thought about indexes shortly after posting - sorry for wasting your time.

I had to migrate existing tables over from DBISAM, where they were used in a pre-existing app.  There were three non-unique indexes which did
not seem to get recreated. I have now done so in the Elevate tables and things have speeded up somewhat.

One thing I note the Elevate DB Manager does not seem to allow you to create non-unique indexes and I had to do it via SQL or am I missing the
obvious again?

thanks again

Tue, Dec 11 2007 9:02 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

L. (pretty name that)
I think you're missing the obvious Smiley

In EDBManger

Pick any table in a database, then in the left hand pane click the + and you'll get a list Columns, Constraints, Indexes (damned yanks - should be Indices) and Triggers

Click on Indexes and you'll be shown a list of existing indices for the table and be given a menu option to create new ones. Click on any index OTHER than the primary key and you can alter or drop it from the menu. The primary key is altered through the alter table menu option.


Roy Lambert
Tue, Dec 11 2007 9:40 AMPermanent Link

L. Duncan
Roy Lambert <roy.lambert@skynet.co.uk> wrote:

L. (pretty name that)
I think you're missing the obvious Smiley

As always.

Thank you once again.

regards
Laing
Tue, Dec 11 2007 1:54 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Laing,

<< I had to migrate existing tables over from DBISAM, where they were used
in a pre-existing app.  There were three non-unique indexes which did not
seem to get recreated. I have now done so in the Elevate tables and things
have speeded up somewhat. >>

Could you send me an empty version of that DBISAM table ?  I'd like to check
that out and see why they weren't migrated over since they should have been.

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Dec 12 2007 4:35 AMPermanent Link

Laing
"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

<<Could you send me an empty version of that DBISAM table ?  I'd like to check
that out and see why they weren't migrated over since they should have been.>>

Tim,

Sorry, I do seem to be wasting everyone's time. Looking at things again, the indices were in fact migrated over on the Database Migrate but lost
during a subsequent SQL 'transfer' to the live database. Entirely down to me.

As you wil have guessed I'm pretty new to Elevate ;o)

thanks again
Laing


Wed, Dec 12 2007 2:41 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Laing,

<< Sorry, I do seem to be wasting everyone's time. Looking at things again,
the indices were in fact migrated over on the Database Migrate but lost
during a subsequent SQL 'transfer' to the live database. Entirely down to
me.

As you wil have guessed I'm pretty new to Elevate ;o) >>

No problem at all.  I'm glad you found the problem.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image