Tim,

It would be great if:
-there was a possibility to edit/change SP's (I guess you now have to drop
first) To view them would also be a possibility because then you can copy
them first.
-there where line numbers in the SQL definition (watch the already included
BEGIN END), because when an error occurs in a long script (creating a db),
you're now totally lost

Regards, Harry

Tim,

> It would be great if:
> -there was a possibility to edit/change SP's (I guess you now have to drop
> first) To view them would also be a possibility because then you can copy
> them first

Same for Views etc.

Regards, Harry




"Harry de Boer" <harry@staaf.nl> schreef in bericht
news:231484B2-C628-4A65-8316-7869F754F61E@news.elevatesoft.com...
> Tim,
>
> It would be great if:
> -there was a possibility to edit/change SP's (I guess you now have to drop
> first) To view them would also be a possibility because then you can copy
> them first.
> -there where line numbers in the SQL definition (watch the already
included
> BEGIN END), because when an error occurs in a long script (creating a db),
> you're now totally lost
>
> Regards, Harry
>
>

Harry,

<< -there was a possibility to edit/change SP's (I guess you now have to
drop first) >>

Initially we're just going with the standard and having ALTERs just modify
the description of any objects (except for tables, of course).  After the
initial release, we'll start fleshing out the SQL with a bit more syntactic
sugar.

<< To view them would also be a possibility because then you can copy them
first. >>

You can - just use this query:

SELECT * FROM Information.Procedures

<< -there where line numbers in the SQL definition (watch the already
included BEGIN END), because when an error occurs in a long script (creating
a db), you're now totally lost >>

Are you referring to the dynamic SQL statement being used in the EXECUTE or
EXECUTE IMMEDIATE statement ?

--
Tim Young
Elevate Software
www.elevatesoft.com

> << -there where line numbers in the SQL definition (watch the already
> included BEGIN END), because when an error occurs in a long script
(creating
> a db), you're now totally lost >>
>
> Are you referring to the dynamic SQL statement being used in the EXECUTE
or
> EXECUTE IMMEDIATE statement ?

Sorry, I mean in the memo (UI) in the SQL tab of a SP.

Harry


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:9B4C974C-D125-4AA2-856D-ECF8DAD9B960@news.elevatesoft.com...
> Harry,
>
> << -there was a possibility to edit/change SP's (I guess you now have to
> drop first) >>
>
> Initially we're just going with the standard and having ALTERs just modify
> the description of any objects (except for tables, of course).  After the
> initial release, we'll start fleshing out the SQL with a bit more
syntactic
> sugar.
>
> << To view them would also be a possibility because then you can copy them
> first. >>
>
> You can - just use this query:
>
> SELECT * FROM Information.Procedures
>
> << -there where line numbers in the SQL definition (watch the already
> included BEGIN END), because when an error occurs in a long script
(creating
> a db), you're now totally lost >>
>
> Are you referring to the dynamic SQL statement being used in the EXECUTE
or
> EXECUTE IMMEDIATE statement ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Harry,

<< Sorry, I mean in the memo (UI) in the SQL tab of a SP. >>

Line and column numbers are handled if there is a compilation error in the
SP, and the cursor should be positioned on the line and column where the
error occurred.  If you have an example where it isn't doing so, please let
me know what the SP code was.

--
Tim Young
Elevate Software
www.elevatesoft.com