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.

Error after Select V 11

2 posts in General Discussion Last posting was on 2009-09-29 12:23:46.0Z
Y RO Posted on 2009-09-24 16:24:48.0Z
Reply-To: "Y RO" <royacov@gmail.com>
From: "Y RO" <royacov@gmail.com>
Newsgroups: ianywhere.public.general
Subject: Error after Select V 11
Lines: 2
Organization: R
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="windows-1255"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 12.0.1606
X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4abb9d50$1@forums-1-dub>
Date: 24 Sep 2009 09:24:48 -0700
X-Trace: forums-1-dub 1253809488 10.22.241.152 (24 Sep 2009 09:24:48 -0700)
X-Original-Trace: 24 Sep 2009 09:24:48 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7744
Article PK: 6785

Dear sir,
In our use and study of the 11.0 version of sybas (developer edition), we
came upon a few problems.

1. When we used the query "select max(datatimefield)", it took about an hour
to finish the proccessing,
while in the 9.0 version it worked fine and takes a few seconds to work,

2. We added a new field to A datebase,
then we activated a procedure which didnt include the new field,
which then made the software work really slow and didnt finish the
proccessing.

3. The queries we use might have minor mistakes,
but those little mistakes jam up the whole software.
is that normal? is there an error log that might help pointing out those
little mistakes?



Thank you & Best regards
M.r


Chris Keating (Sybase iAnywhere) Posted on 2009-09-29 12:23:46.0Z
From: "Chris Keating (Sybase iAnywhere)" <keating_nospam@sybase.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: Error after Select V 11
References: <4abb9d50$1@forums-1-dub>
In-Reply-To: <4abb9d50$1@forums-1-dub>
Content-Type: text/plain; charset=windows-1255; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4ac1fc52$1@forums-1-dub>
Date: 29 Sep 2009 05:23:46 -0700
X-Trace: forums-1-dub 1254227026 10.22.241.152 (29 Sep 2009 05:23:46 -0700)
X-Original-Trace: 29 Sep 2009 05:23:46 -0700, vip152.sybase.com
Lines: 44
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:7748
Article PK: 6791


> 1. When we used the query "select max(datatimefield)", it took about an hour to finish the proccessing,
> while in the 9.0 version it worked fine and takes a few seconds to work,

Can you post the query plan? To do so,
1. Open DBISQL
2. Enter the statement into the SQL Statements pane (or you do so in the
plan viewer)
3. Select Tools | Plan View (or Shift-F5)
4. Set the Statistics Level to "Detailed and Node Statistics"
5. Click "Get Plan"
6. Click "Save As" to save the plan
7. Attach the plan for review.

> 2. We added a new field to A datebase,
> then we activated a procedure which didnt include the new field,Pl
> which then made the software work really slow and didnt finish the proccessing.

Need more specific detail here. Can this behaviour be reproduced? Can
you isolate where the procedure is slow?


Y RO wrote:
> Dear sir,
> In our use and study of the 11.0 version of sybas (developer edition),
> we came upon a few problems.
>
> 1. When we used the query "select max(datatimefield)", it took about an
> hour to finish the proccessing,
> while in the 9.0 version it worked fine and takes a few seconds to work,
>
> 2. We added a new field to A datebase,
> then we activated a procedure which didnt include the new field,
> which then made the software work really slow and didnt finish the
> proccessing.
>
> 3. The queries we use might have minor mistakes,
> but those little mistakes jam up the whole software.
> is that normal? is there an error log that might help pointing out those
> little mistakes?
>
>
>
> Thank you & Best regards
> M.r