Subject | RE: [firebird-support] tracking progress of a SP |
---|---|
Author | Nigel Weeks |
Post date | 2005-03-20T22:57:25Z |
Why not use the event posting and handling of Firebird?
Get your Stored Procedure to post events as it processes, and use another
program to 'watch' the events...
No extra storage tables, no fighting with 'now' and CURRENT_TIME issues...
It'd be a very useful utility if someone wanted to write one...;-)
Nige.
Get your Stored Procedure to post events as it processes, and use another
program to 'watch' the events...
No extra storage tables, no fighting with 'now' and CURRENT_TIME issues...
It'd be a very useful utility if someone wanted to write one...;-)
Nige.
> -----Original Message-----
> From: David Johnson [mailto:d_johnson@...]
> Sent: Monday, 21 March 2005 9:49 AM
> To: firebird-support@yahoogroups.com
> Subject: RE: [firebird-support] tracking progress of a SP
>
>
> It would be nice if there were instrumentation something like
> that provided by Platinum for DB2.
>
> Another thing to add to my wish-list / to-do eventually list.
>
> Sigh
>
> On Mon, 2005-03-21 at 08:44 +1100, Alan McDonald wrote:
> >
> > I was trying to track the internal progress of a SP that
> was running
> > quite slow.
> >
> > I created an external table, then wrote to the table at
> various points
> > from within the SP and updated using CURRENT_TIME and a
> note field.
> > Of course, as I later learned from the documentation the
> CURRENT_TIME
> > was set at the beginning of the SP and never incremented.
> >
> > I finally figured out what was causing the slow processing, but I
> > would like to know for the future if something like this is
> possible.
> > I tried to Google, but only got information as to why it
> doesn't work.
> >
> > Is there any way to get a real CURRENT_TIME from within a SP?
> >
> > Thanks,
> >
> > Rick
> >
> > use 'NOW' instead of CURRENT_TIME
> > Alan
> >
> >
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>
>
>
> __________ NOD32 1.1030 (20050319) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.nod32.com
>
>