Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

query keysize?

2 posts in Objects Last posting was on 2003-04-11 06:37:17.0Z
Henry Posted on 2003-04-09 20:43:58.0Z
Newsgroups: sybase.public.powerbuilder.objects
From: HENRY
Date: Wed, 9 Apr 2003 16:43:58 -0400
Subject: query keysize?
Lines: 8
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <364_5641AE908D69640C0071E3C385256D03.0071E3D285256D03@webforums>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.powerbuilder.objects:7314
Article PK: 734607

we recently upgraded to 8.0 and a rather large query that used to run fine
is now erroring with the message saying that the keysize is too large.
seems the limit is 600 and mine is 603.

what is the "key size" referring to? what should i try to trim down to
make this thing work?

please advise.


Sanjiv Das [TeamSybase] Posted on 2003-04-11 06:37:17.0Z
Newsgroups: sybase.public.powerbuilder.objects
From: "Sanjiv Das [TeamSybase]" <No-Spam-SDas_TeamSybase@HotMail.Com>
Subject: Re: query keysize?
Date: Thu, 10 Apr 2003 23:37:17 -0700
Lines: 33
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-Mimeole: Produced By Microsoft MimeOLE V6.00.2800.1106
NNTP-Posting-Host: ip68-101-97-153.oc.oc.cox.net 68.101.97.153
Message-ID: <364_OSq18V$$CHA.278@forums-2-dub>
References: <364_5641AE908D69640C0071E3C385256D03.0071E3D285256D03@webforums>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums-2-dub.sybase.com
Xref: forums-1-dub sybase.public.powerbuilder.objects:7315
Article PK: 734604

Henry,

Did you change something in the database too at the same time as the PB
upgrade ? Column lengths ? Index attributes ?

Typically I've seen keysize in relation to a database meaning the size of
the keys in an index. This is calculated based on the number and data type
of columns that make up the index.

What DBMS are you using ? Have you tried the same query outside of PB ? Run
a trace on the database interaction of the PB app and take the query from
there and run that in a native SQL environment.

Please also note that some DBMSs generate indexes for temporary work tables
that are created internally when running a query. There may be a problem in
those tables or keys too.

Sanjiv.

<HENRY> wrote in message
news:5641AE908D69640C0071E3C385256D03.0071E3D285256D03@webforums...
> we recently upgraded to 8.0 and a rather large query that used to run fine
> is now erroring with the message saying that the keysize is too large.
> seems the limit is 600 and mine is 603.
>
> what is the "key size" referring to? what should i try to trim down to
> make this thing work?
>
> please advise.