Although the consolidation is a stored procedure, the processing of it
is not. If you simply run a "consolidation 1", you'll probably get a
lot of records back. We are working on an alternative solution to being
able to schedule this.
What Graeme is talking about is rather than put the query into the
scheduler, create a stored procedure containing the query. Then
just put the name of the stored procedure into the TSQL text box
for the scheduler. You can test the proc but typing just the name
is query manager and executing.
The cool thing about stored procedures is that you can access
them from defined remote servers. We do this a lot to move
or manually replicate information.
> -----Original Message-----
> From: Graeme Slogrove <graeme@fdd.net>
> To: emerald@emerald.iea.com <emerald@emerald.iea.com>
> Date: Friday, February 13, 1998 3:06 PM
> Subject: Re: Scheduled LONG queries
>
> >
> >> As we evolve our Emerald installation, we have started to require
> >> increasingly more complex TSQL statements to be run on a scheduled
> >basis.
> >> The 256 character limit is starting to cause problems.
> >
> >Try rather writing these as stored procedures. Them simply call the SP
> >from the Task Manager, hoping of course that you haven't named your
> >task with a name of more than 256 characters ;)
> >
> >Cheers!
> > Graeme
> >
> >
> >----
> >Posted by WebMail
> >
> >
> > ----------------------------------------------------------
> > Emerald Mailing List listserver@emerald.iea.com
> >
> >
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com