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.

Issues with debugging Stored procedures in V2.1 for ASE

11 posts in General Discussion Last posting was on 2009-03-04 07:39:40.0Z
KK Bevin Posted on 2009-02-05 17:45:24.0Z
Sender: ac6.498b2040.1804289383@sybase.com
From: KK Bevin
Newsgroups: sybase.public.workspace.general
Subject: Issues with debugging Stored procedures in V2.1 for ASE
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <498b25b4.b3b.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 5 Feb 2009 09:45:24 -0800
X-Trace: forums-1-dub 1233855924 10.22.241.41 (5 Feb 2009 09:45:24 -0800)
X-Original-Trace: 5 Feb 2009 09:45:24 -0800, 10.22.241.41
Lines: 56
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:794
Article PK: 1088475

Hi SybaseWorkspace team,

I was overjoyed when i looked at the option for debugging
sybase stored procedures through workpace. We are using ASE
12.5 and we have lot of stored procedures. But when i use
the 2.1 version of workspace i am not able to get the
features mentioned in tutorial for stored procedure
debugging.

One major issue was that i cant debug the stored procedures
that i see in my database. I am logging as a database owner.
I can execute the stored procedure. I can even create
breakpoints and when i click on debug then the SP executes
without stopping at the breakpoints.
Then the alternate way that i tried was i copied the source
of the same SP and created a new one with different name.
The name of the stored procedure was adjusted to be less
than 12 characters for the stored procedure. After creating
the new stored procedure then i was able to debug the stored
procedure.
But this is really an annoying issue as most of the stored
procedures are more than 12 characters long and for me to
change the name will be very tedious. Also we have thousands
of SP in the database !!!
Is there anything that i have missed in the configuration
option for debugging. Please let me know as it would be of
great help for me.

The second major issue is that i am not able to see the
#tables (temporary tables) in Sybase stored procedure while
debugging.
This really defeats my purpose of debugging as i have to put
select statement in between to see the output of the
#tables.
It is strange that i am able to see regular tables in the
referenced tables section but i am not able to see the #
tables there.
I even watched the online video presentation to debug the
stored procedure and followed the same steps.

I found a major point for both the issues that i am
reporting here. The tutorial or video that Sybase give for
debugging in of version 2.0 and i have downloaded the 2.1
version of sybase workspace.
Is these features not available in 2.1 ? ( i dont think so
).

Please help with this issue as i dont want to search for any
other tool for Sybase database management if these issues
are fixed.

Thanks,
KK


Teh


Pieter Coene Posted on 2009-02-06 07:15:32.0Z
Sender: 1c9b.4986c27e.1804289383@sybase.com
From: Pieter Coene
Newsgroups: sybase.public.workspace.general
Subject: Re: Issues with debugging Stored procedures in V2.1 for ASE
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <498be394.1d25.1681692777@sybase.com>
References: <498b25b4.b3b.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 5 Feb 2009 23:15:32 -0800
X-Trace: forums-1-dub 1233904532 10.22.241.41 (5 Feb 2009 23:15:32 -0800)
X-Original-Trace: 5 Feb 2009 23:15:32 -0800, 10.22.241.41
Lines: 77
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:796
Article PK: 1088476

Hi KK Bevin,

these two issues are known issues with Sybase. I've reported
them some time ago.

- About the long procedure name, we had the same problem,
upgrading to 15.0.2 solved it. (maybe a 12.5 with a latest
EBF can solve it too, but thats for a sybase technical to
confirm)

- Debugging (querying) # tables is the main reason why we
want to debug procedures. (I don't want to see my regular
tables, i can retrieve them in my normal sql editor). I've
been asking for this feature since Workspace 1.0. I know i'm
not the only one wanting this. I must say, i don't know the
status of this issue, so again, i'll let the sybase
technical answer...

greetz
Pieter

> Hi SybaseWorkspace team,
>
> I was overjoyed when i looked at the option for debugging
> sybase stored procedures through workpace. We are using
> ASE 12.5 and we have lot of stored procedures. But when i
> use the 2.1 version of workspace i am not able to get the
> features mentioned in tutorial for stored procedure
> debugging.
>
> One major issue was that i cant debug the stored
> procedures that i see in my database. I am logging as a
> database owner. I can execute the stored procedure. I can
> even create breakpoints and when i click on debug then the
> SP executes without stopping at the breakpoints.
> Then the alternate way that i tried was i copied the
> source of the same SP and created a new one with different
> name. The name of the stored procedure was adjusted to be
> less than 12 characters for the stored procedure. After
> creating the new stored procedure then i was able to debug
> the stored procedure.
> But this is really an annoying issue as most of the stored
> procedures are more than 12 characters long and for me to
> change the name will be very tedious. Also we have
> thousands of SP in the database !!!
> Is there anything that i have missed in the configuration
> option for debugging. Please let me know as it would be of
> great help for me.
>
> The second major issue is that i am not able to see the
> #tables (temporary tables) in Sybase stored procedure
> while debugging.
> This really defeats my purpose of debugging as i have to
> put select statement in between to see the output of the
> #tables.
> It is strange that i am able to see regular tables in the
> referenced tables section but i am not able to see the #
> tables there.
> I even watched the online video presentation to debug the
> stored procedure and followed the same steps.
>
> I found a major point for both the issues that i am
> reporting here. The tutorial or video that Sybase give for
> debugging in of version 2.0 and i have downloaded the 2.1
> version of sybase workspace.
> Is these features not available in 2.1 ? ( i dont think so
> ).
>
> Please help with this issue as i dont want to search for
> any other tool for Sybase database management if these
> issues are fixed.
>
> Thanks,
> KK
>
>
> Teh


Li huang [Sybase] Posted on 2009-02-06 07:53:16.0Z
From: "Li huang [Sybase]" <lihuang@sybase.com>
Reply-To: lihuang@sybase.com
Organization: Sybase Software Co., Ltd
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
Newsgroups: sybase.public.workspace.general
Subject: Re: Issues with debugging Stored procedures in V2.1 for ASE
References: <498b25b4.b3b.1681692777@sybase.com>
In-Reply-To: <498b25b4.b3b.1681692777@sybase.com>
Content-Type: multipart/mixed; boundary="------------050401070100090702050306"
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <498bec6c@forums-1-dub>
Date: 5 Feb 2009 23:53:16 -0800
X-Trace: forums-1-dub 1233906796 10.22.241.152 (5 Feb 2009 23:53:16 -0800)
X-Original-Trace: 5 Feb 2009 23:53:16 -0800, vip152.sybase.com
Lines: 1950
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:797
Article PK: 1088536

Hi, KK:

Thank you for your feedbacks!

1. To debug a stored procedure in ASE12, the identifier has a maximum length of 20 bytes for SQL Debugger to work correctly.
And you can upgrade to 15.0.2 to solve it as Pieter mentioned above.
2. I can't reproduce your second issue. Please see the attached pic. Or you may give us the detailed reproduce steps.
3. All features in WorkSpace 2.0 are also available in WorkSpace 2.1.


--
Thanks and regards,

Daniel(Li) Huang [Sybase]

Sybase
Sybase Software (China) Co., Ltd
Room 1202-1203, Building One,
Zhangjiang Semiconductor Industry Park
3000 Longdong Avenue
Pudong, Shanghai 201203
Tel 8621-38657420
Email: lihuang@sybase.com

tempTable.JPG

KK Bevin Posted on 2009-02-07 01:14:15.0Z
Sender: 3751.498cdb71.1804289383@sybase.com
From: KK Bevin
Newsgroups: sybase.public.workspace.general
Subject: Re: Issues with debugging Stored procedures in V2.1 for ASE
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <498ce067.37ab.1681692777@sybase.com>
References: <498bec6c@forums-1-dub>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-=_forums-1-dub498ce067"
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 6 Feb 2009 17:14:15 -0800
X-Trace: forums-1-dub 1233969255 10.22.241.41 (6 Feb 2009 17:14:15 -0800)
X-Original-Trace: 6 Feb 2009 17:14:15 -0800, 10.22.241.41
Lines: 4464
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:798
Article PK: 1088537

Hi Daniel,

Thanks for your response.

So the only solution for the issue no:1 seems to be database
ASE upgrade. Well... that is not a major problem as i have
the workaround to rename the SP to a smaller name.

Regarding the second issue, I am attaching the screen shot
of my sybase workspace 2.1 while debugging.
You can see that there is no temp tables in the reference
tables section of the debugging perspective. In the result
window you can see the records inserted into the table
through SP.

Are you using Workspace 2.0 or 2.1?

If you are using 2.0 then please try the same with 2.1 and
see if you are getting the issue.

If you are using 2.1 then please give me the link for the
software download. I want to make sure that I have the same
product that you have. Then I can check if i can see the
temp tables.

Please share your answers.

Peiter,

Thanks a lot for your comments.
Atleast I am not alone with the #temp table issue with
workspace.

Regards,
KK

> Hi, KK:
>
> Thank you for your feedbacks!
>
> 1. To debug a stored procedure in ASE12, the identifier
> has a maximum length of 20 bytes for SQL Debugger to work
> correctly. And you can upgrade to 15.0.2 to solve it as
> Pieter mentioned above. 2. I can't reproduce your second
> issue. Please see the attached pic. Or you may give us the
> detailed reproduce steps. 3. All features in WorkSpace 2.0
> are also available in WorkSpace 2.1.
>
>
> --
> Thanks and regards,
>
> Daniel(Li) Huang [Sybase]
>
> Sybase
> Sybase Software (China) Co., Ltd
> Room 1202-1203, Building One,
> Zhangjiang Semiconductor Industry Park
> 3000 Longdong Avenue
> Pudong, Shanghai 201203
> Tel 8621-38657420
> Email: lihuang@sybase.com
>
>
> [Attachment: tempTable.JPG]

sybase workspace issue.JPG