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.

Stopped using Workspace for production...(for now)

4 posts in General Discussion Last posting was on 2007-07-27 13:08:45.0Z
JR Posted on 2007-07-25 20:58:09.0Z
Sender: 1374.469ba0ef.1804289383@sybase.com
From: JR
Newsgroups: sybase.public.workspace.general
Subject: Stopped using Workspace for production...(for now)
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <46a7b961.4b4.1681692777@sybase.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 25 Jul 2007 13:58:09 -0700
X-Trace: forums-1-dub 1185397089 10.22.241.41 (25 Jul 2007 13:58:09 -0700)
X-Original-Trace: 25 Jul 2007 13:58:09 -0700, 10.22.241.41
Lines: 74
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:477
Article PK: 1088160

I attempted to use Workspace on a recent Sybase IQ
production promote (instead of DBISQL). Here is what I
encountered (I’m venting here):

1. When copy and pasting DML/DDL from our source safe
system for promotion to production workspace replaced text;
i.e. changed 'commit' to 'commit work'. what else could get
changed?

2. When running a SQL statement that should have resulted
in a duplicate key error workspace didn't report an error,
rather, success for all statements.

3. When trying to compile a stored procedure sometimes it
would compile, sometimes it wouldn't. complained about a
syntax error near ‘;’… without consistency. There
wasn’t a ‘;’ anywhere in the text. All I did to get
it to compile was to re-execute the exact same text several
times from within the same window. Received this behavior
with several stored procs.

4. I executed 3 SQL statements separated by 'go'. The
first and third statement got executed. The second
statement did not. No error received. I could only get the
second statement to execute by commenting out the first and
third.

I know you’re thinking, I must have been doing something
wrong, right? Wrong!

*** Resolution *** Simply reverted back to using DBISQL,
following the exact same steps, and all the issues above did
not occur.

Several of us are using Workspace for IQ and ASE…we all
have been somewhat frustrated with the flaky, and more
importantly, inconsistent behavior so far.




Other things we found (maybe we’re missing something on
these):

1. When trying to view dbo owned stored procedures on IQ
(without being dbo), the ‘normal’ sql editor can’t
open the procedure for viewing…can only see the text from
some greyed out properties window in Workspace. I suppose
the user needs full perms on the stored proc to view it in
the editor even if they are just viewing it not editing it??

2. When viewing the results grid the scroll bar doesn’t
work, i.e. it can cover up the last row of data, it won’t
let you view/expand the last column to see it, etc.

3. When we close Workspace (the whole app), and then
re-open the app we get the error ‘Workspace is in
use...’ only way to open Workspace again is to terminate
javaw.exe from taskmgr.

4. The wrong stored proc gets executed. The scenario: two
sql files are opened. Each contain a different ‘exec
stored proc’. When you execute the first one it runs
fine. When you go to the second file and run the other
stored proc, it runs the first stored proc on the first
file, again.

5. Debugger displays the same behavior as above (4). Have
to fight with it to get it to debug the correct stored proc.


lastly- ok let's say we are being stupid here and we are
causing all the issues above...then Workspace isn't very
intuitive .


Mike Crocker Posted on 2007-07-26 21:34:44.0Z
From: "Mike Crocker" <crocker@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <46a7b961.4b4.1681692777@sybase.com>
Subject: Re: Stopped using Workspace for production...(for now)
Lines: 86
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
NNTP-Posting-Host: crockerxp.sybase.com
X-Original-NNTP-Posting-Host: crockerxp.sybase.com
Message-ID: <46a91374$2@forums-1-dub>
Date: 26 Jul 2007 14:34:44 -0700
X-Trace: forums-1-dub 1185485684 10.24.112.185 (26 Jul 2007 14:34:44 -0700)
X-Original-Trace: 26 Jul 2007 14:34:44 -0700, crockerxp.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:478
Article PK: 1088161

I apologize for the frustrating issues you're seeing with WorkSpace. It's
important to me that we get to the bottom of these issues. I hope you're
willing to supply more info to help us out. If so, please contact me
directly at 603-230-7127 or crocker@sybase.com

Mike Crocker
Engineering Director


<JR> wrote in message news:46a7b961.4b4.1681692777@sybase.com...
I attempted to use Workspace on a recent Sybase IQ
production promote (instead of DBISQL). Here is what I
encountered (I'm venting here):

1. When copy and pasting DML/DDL from our source safe
system for promotion to production workspace replaced text;
i.e. changed 'commit' to 'commit work'. what else could get
changed?

2. When running a SQL statement that should have resulted
in a duplicate key error workspace didn't report an error,
rather, success for all statements.

3. When trying to compile a stored procedure sometimes it
would compile, sometimes it wouldn't. complained about a
syntax error near ';'. without consistency. There
wasn't a ';' anywhere in the text. All I did to get
it to compile was to re-execute the exact same text several
times from within the same window. Received this behavior
with several stored procs.

4. I executed 3 SQL statements separated by 'go'. The
first and third statement got executed. The second
statement did not. No error received. I could only get the
second statement to execute by commenting out the first and
third.

I know you're thinking, I must have been doing something
wrong, right? Wrong!

*** Resolution *** Simply reverted back to using DBISQL,
following the exact same steps, and all the issues above did
not occur.

Several of us are using Workspace for IQ and ASE.we all
have been somewhat frustrated with the flaky, and more
importantly, inconsistent behavior so far.




Other things we found (maybe we're missing something on
these):

1. When trying to view dbo owned stored procedures on IQ
(without being dbo), the 'normal' sql editor can't
open the procedure for viewing.can only see the text from
some greyed out properties window in Workspace. I suppose
the user needs full perms on the stored proc to view it in
the editor even if they are just viewing it not editing it??

2. When viewing the results grid the scroll bar doesn't
work, i.e. it can cover up the last row of data, it won't
let you view/expand the last column to see it, etc.

3. When we close Workspace (the whole app), and then
re-open the app we get the error 'Workspace is in
use...' only way to open Workspace again is to terminate
javaw.exe from taskmgr.

4. The wrong stored proc gets executed. The scenario: two
sql files are opened. Each contain a different 'exec
stored proc'. When you execute the first one it runs
fine. When you go to the second file and run the other
stored proc, it runs the first stored proc on the first
file, again.

5. Debugger displays the same behavior as above (4). Have
to fight with it to get it to debug the correct stored proc.


lastly- ok let's say we are being stupid here and we are
causing all the issues above...then Workspace isn't very
intuitive .


JR Posted on 2007-07-26 21:51:29.0Z
Sender: 2601.46a8e891.1804289383@sybase.com
From: JR
Newsgroups: sybase.public.workspace.general
Subject: Re: Stopped using Workspace for production...(for now)
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <46a91761.2b58.1681692777@sybase.com>
References: <46a91374$2@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 26 Jul 2007 14:51:29 -0700
X-Trace: forums-1-dub 1185486689 10.22.241.41 (26 Jul 2007 14:51:29 -0700)
X-Original-Trace: 26 Jul 2007 14:51:29 -0700, 10.22.241.41
Lines: 93
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:479
Article PK: 1088162

thanks mike, hope I didn't seem to negative :) are you
going to be at techwave? if not i'll call you. thanks!

> I apologize for the frustrating issues you're seeing with
> WorkSpace. It's important to me that we get to the
> bottom of these issues. I hope you're willing to supply
> more info to help us out. If so, please contact me
> directly at 603-230-7127 or crocker@sybase.com
>
> Mike Crocker
> Engineering Director
>
>
> <JR> wrote in message
> news:46a7b961.4b4.1681692777@sybase.com... I attempted to
> use Workspace on a recent Sybase IQ production promote
> (instead of DBISQL). Here is what I encountered (I'm
> venting here):
>
> 1. When copy and pasting DML/DDL from our source safe
> system for promotion to production workspace replaced text
> ; i.e. changed 'commit' to 'commit work'. what else could
> get changed?
>
> 2. When running a SQL statement that should have resulted
> in a duplicate key error workspace didn't report an error,
> rather, success for all statements.
>
> 3. When trying to compile a stored procedure sometimes it
> would compile, sometimes it wouldn't. complained about a
> syntax error near ';'. without consistency. There
> wasn't a ';' anywhere in the text. All I did to get
> it to compile was to re-execute the exact same text
> several times from within the same window. Received this
> behavior with several stored procs.
>
> 4. I executed 3 SQL statements separated by 'go'. The
> first and third statement got executed. The second
> statement did not. No error received. I could only get
> the second statement to execute by commenting out the
> first and third.
>
> I know you're thinking, I must have been doing something
> wrong, right? Wrong!
>
> *** Resolution *** Simply reverted back to using DBISQL,
> following the exact same steps, and all the issues above
> did not occur.
>
> Several of us are using Workspace for IQ and ASE.we all
> have been somewhat frustrated with the flaky, and more
> importantly, inconsistent behavior so far.
>
>
>
>
> Other things we found (maybe we're missing something on
> these):
>
> 1. When trying to view dbo owned stored procedures on IQ
> (without being dbo), the 'normal' sql editor can't
> open the procedure for viewing.can only see the text from
> some greyed out properties window in Workspace. I suppose
> the user needs full perms on the stored proc to view it in
> the editor even if they are just viewing it not editing
> it??
>
> 2. When viewing the results grid the scroll bar doesn't
> work, i.e. it can cover up the last row of data, it won't
> let you view/expand the last column to see it, etc.
>
> 3. When we close Workspace (the whole app), and then
> re-open the app we get the error 'Workspace is in
> use...' only way to open Workspace again is to terminate
> javaw.exe from taskmgr.
>
> 4. The wrong stored proc gets executed. The scenario:
> two sql files are opened. Each contain a different 'exec
> stored proc'. When you execute the first one it runs
> fine. When you go to the second file and run the other
> stored proc, it runs the first stored proc on the first
> file, again.
>
> 5. Debugger displays the same behavior as above (4).
> Have to fight with it to get it to debug the correct
> stored proc.
>
>
> lastly- ok let's say we are being stupid here and we are
> causing all the issues above...then Workspace isn't very
> intuitive .
>
>


Mike Crocker Posted on 2007-07-27 13:08:45.0Z
From: "Mike Crocker" <crocker@sybase.com>
Newsgroups: sybase.public.workspace.general
References: <46a91374$2@forums-1-dub> <46a91761.2b58.1681692777@sybase.com>
Subject: Re: Stopped using Workspace for production...(for now)
Lines: 104
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.3138
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
NNTP-Posting-Host: crockerxp.sybase.com
X-Original-NNTP-Posting-Host: crockerxp.sybase.com
Message-ID: <46a9ee5d$1@forums-1-dub>
Date: 27 Jul 2007 06:08:45 -0700
X-Trace: forums-1-dub 1185541725 10.24.112.185 (27 Jul 2007 06:08:45 -0700)
X-Original-Trace: 27 Jul 2007 06:08:45 -0700, crockerxp.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.workspace.general:480
Article PK: 1088164

Yes, I'm going to be at techwave.

In the meantime, we already have QA running through these issues. May they
send you emails directly if they have questions?

thanks,
mike

<JR> wrote in message news:46a91761.2b58.1681692777@sybase.com...
> thanks mike, hope I didn't seem to negative :) are you
> going to be at techwave? if not i'll call you. thanks!
>
>> I apologize for the frustrating issues you're seeing with
>> WorkSpace. It's important to me that we get to the
>> bottom of these issues. I hope you're willing to supply
>> more info to help us out. If so, please contact me
>> directly at 603-230-7127 or crocker@sybase.com
>>
>> Mike Crocker
>> Engineering Director
>>
>>
>> <JR> wrote in message
>> news:46a7b961.4b4.1681692777@sybase.com... I attempted to
>> use Workspace on a recent Sybase IQ production promote
>> (instead of DBISQL). Here is what I encountered (I'm
>> venting here):
>>
>> 1. When copy and pasting DML/DDL from our source safe
>> system for promotion to production workspace replaced text
>> ; i.e. changed 'commit' to 'commit work'. what else could
>> get changed?
>>
>> 2. When running a SQL statement that should have resulted
>> in a duplicate key error workspace didn't report an error,
>> rather, success for all statements.
>>
>> 3. When trying to compile a stored procedure sometimes it
>> would compile, sometimes it wouldn't. complained about a
>> syntax error near ';'. without consistency. There
>> wasn't a ';' anywhere in the text. All I did to get
>> it to compile was to re-execute the exact same text
>> several times from within the same window. Received this
>> behavior with several stored procs.
>>
>> 4. I executed 3 SQL statements separated by 'go'. The
>> first and third statement got executed. The second
>> statement did not. No error received. I could only get
>> the second statement to execute by commenting out the
>> first and third.
>>
>> I know you're thinking, I must have been doing something
>> wrong, right? Wrong!
>>
>> *** Resolution *** Simply reverted back to using DBISQL,
>> following the exact same steps, and all the issues above
>> did not occur.
>>
>> Several of us are using Workspace for IQ and ASE.we all
>> have been somewhat frustrated with the flaky, and more
>> importantly, inconsistent behavior so far.
>>
>>
>>
>>
>> Other things we found (maybe we're missing something on
>> these):
>>
>> 1. When trying to view dbo owned stored procedures on IQ
>> (without being dbo), the 'normal' sql editor can't
>> open the procedure for viewing.can only see the text from
>> some greyed out properties window in Workspace. I suppose
>> the user needs full perms on the stored proc to view it in
>> the editor even if they are just viewing it not editing
>> it??
>>
>> 2. When viewing the results grid the scroll bar doesn't
>> work, i.e. it can cover up the last row of data, it won't
>> let you view/expand the last column to see it, etc.
>>
>> 3. When we close Workspace (the whole app), and then
>> re-open the app we get the error 'Workspace is in
>> use...' only way to open Workspace again is to terminate
>> javaw.exe from taskmgr.
>>
>> 4. The wrong stored proc gets executed. The scenario:
>> two sql files are opened. Each contain a different 'exec
>> stored proc'. When you execute the first one it runs
>> fine. When you go to the second file and run the other
>> stored proc, it runs the first stored proc on the first
>> file, again.
>>
>> 5. Debugger displays the same behavior as above (4).
>> Have to fight with it to get it to debug the correct
>> stored proc.
>>
>>
>> lastly- ok let's say we are being stupid here and we are
>> causing all the issues above...then Workspace isn't very
>> intuitive .
>>
>>