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.

migrate from pb9 to pb11; datawindow table scans

7 posts in DataWindow Last posting was on 2008-08-07 20:21:17.0Z
JR Posted on 2008-08-05 15:48:23.0Z
Sender: 31cc.48987002.1804289383@sybase.com
From: JR
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: migrate from pb9 to pb11; datawindow table scans
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <48987647.32fc.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 5 Aug 2008 08:48:23 -0700
X-Trace: forums-1-dub 1217951303 10.22.241.41 (5 Aug 2008 08:48:23 -0700)
X-Original-Trace: 5 Aug 2008 08:48:23 -0700, 10.22.241.41
Lines: 15
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87494
Article PK: 416750

Any idea why a datawindow migrated from pb9 to 11 would
result in a table scan versus index? the same datawindow in
pb9, when run against the same database, uses all indexes,
no table scan.

when we grab the sql from the datawindow and convert the
retrieval argument to the correct datatype and run by hand
the index is used. it's like the pb11 datawindow is passing
in the wrong datatype arg...even though it is correctly
defined and works in pb9. one note, debug shows the arg.
being passed as '@parm1' not the real value.

We tinkered with the staticbind property with no luck.

any ideas??


M. Searer Posted on 2008-08-05 22:51:24.0Z
From: "M. Searer" <nospam@nospam.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <48987647.32fc.1681692777@sybase.com>
In-Reply-To: <48987647.32fc.1681692777@sybase.com>
Subject: Re: migrate from pb9 to pb11; datawindow table scans
Lines: 22
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4898d96c$1@forums-1-dub>
Date: 5 Aug 2008 15:51:24 -0700
X-Trace: forums-1-dub 1217976684 10.22.241.152 (5 Aug 2008 15:51:24 -0700)
X-Original-Trace: 5 Aug 2008 15:51:24 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87497
Article PK: 416752

what database
what database driver
what datatype is the arg
what datatype is the column

"JR" wrote in message news:48987647.32fc.1681692777@sybase.com...
> Any idea why a datawindow migrated from pb9 to 11 would
> result in a table scan versus index? the same datawindow in
> pb9, when run against the same database, uses all indexes,
> no table scan.
>
> when we grab the sql from the datawindow and convert the
> retrieval argument to the correct datatype and run by hand
> the index is used. it's like the pb11 datawindow is passing
> in the wrong datatype arg...even though it is correctly
> defined and works in pb9. one note, debug shows the arg.
> being passed as '@parm1' not the real value.
>
> We tinkered with the staticbind property with no luck.
>
> any ideas??


JR Posted on 2008-08-06 14:35:10.0Z
Sender: 44e9.4898d75e.1804289383@sybase.com
From: JR
Newsgroups: sybase.public.powerbuilder.datawindow
Subject: Re: migrate from pb9 to pb11; datawindow table scans
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4899b69e.632b.1681692777@sybase.com>
References: <4898d96c$1@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 6 Aug 2008 07:35:10 -0700
X-Trace: forums-1-dub 1218033310 10.22.241.41 (6 Aug 2008 07:35:10 -0700)
X-Original-Trace: 6 Aug 2008 07:35:10 -0700, 10.22.241.41
Lines: 24
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87500
Article PK: 416754


> what database -> Adaptive Server Enterprise/12.5.3/EBF
13057 ESD#5
> what database driver -> going through Jaguar 5.5.0 Build
55012
> what datatype is the arg -> number
> what datatype is the column -> numeric(18,0)
>
>
> "JR" wrote in message
> > news:48987647.32fc.1681692777@sybase.com... Any idea why
> > a datawindow migrated from pb9 to 11 would result in a
> > table scan versus index? the same datawindow in pb9,
> > when run against the same database, uses all indexes, no
> > table scan.
> > when we grab the sql from the datawindow and convert the
> > retrieval argument to the correct datatype and run by
> > hand the index is used. it's like the pb11 datawindow
> > is passing in the wrong datatype arg...even though it is
> > correctly defined and works in pb9. one note, debug
> > shows the arg. being passed as '@parm1' not the real
> > value.
> > We tinkered with the staticbind property with no luck.
> >
> > any ideas??


M. Searer Posted on 2008-08-06 15:21:55.0Z
From: "M. Searer" <nospam@nospam.com>
Newsgroups: sybase.public.powerbuilder.datawindow
References: <4898d96c$1@forums-1-dub> <4899b69e.632b.1681692777@sybase.com>
In-Reply-To: <4899b69e.632b.1681692777@sybase.com>
Subject: Re: migrate from pb9 to pb11; datawindow table scans
Lines: 39
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6001.18000
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4899c193$1@forums-1-dub>
Date: 6 Aug 2008 08:21:55 -0700
X-Trace: forums-1-dub 1218036115 10.22.241.152 (6 Aug 2008 08:21:55 -0700)
X-Original-Trace: 6 Aug 2008 08:21:55 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.powerbuilder.datawindow:87502
Article PK: 416759

so you are not connecting directly to the database? You are going through EAServer (jaguar) to do your retrieve, then getting the
results and putting them into the datawindow?
Or do you mean you are running your datawindow in jaguar/EAServer?

In either case, try running the datawindow from pb directly attached to the database using the sybase native drivers (SYC) and see
how that performance is.

If it is using the indexes (datatypes correctly sent), then the problem is with jaguar/EAserver and you should ask in that forum.
You should also find out how jaguar/easerver is connecting to the database - native drivers, odbc or whatever

"JR" wrote in message news:4899b69e.632b.1681692777@sybase.com...
>> what database -> Adaptive Server Enterprise/12.5.3/EBF
> 13057 ESD#5
>> what database driver -> going through Jaguar 5.5.0 Build
> 55012
>> what datatype is the arg -> number
>> what datatype is the column -> numeric(18,0)
>>
>>
>> "JR" wrote in message
>> > news:48987647.32fc.1681692777@sybase.com... Any idea why
>> > a datawindow migrated from pb9 to 11 would result in a
>> > table scan versus index? the same datawindow in pb9,
>> > when run against the same database, uses all indexes, no
>> > table scan.
>> > when we grab the sql from the datawindow and convert the
>> > retrieval argument to the correct datatype and run by
>> > hand the index is used. it's like the pb11 datawindow
>> > is passing in the wrong datatype arg...even though it is
>> > correctly defined and works in pb9. one note, debug
>> > shows the arg. being passed as '@parm1' not the real
>> > value.
>> > We tinkered with the staticbind property with no luck.
>> >
>> > any ideas??