Subject | Re: Performance of the count Function. |
---|---|
Author | Adam |
Post date | 2005-02-28T23:47:44Z |
--- In firebird-support@yahoogroups.com, "Nigel Weeks" <nweeks@e...>
wrote:
<Begin Dreamland>
It would be nice to have these commands stored in the fdb. I have a
couple of SPs that do some general maintenance. They don't do
anything critical, but if they are not run at some ungodly hour in
the morning, they will run the next time the user uses particular
functions, which slows it down. The reason it is preferable (to me)
is that when we get a new customer, it would be much easier to
preload this schedule in our "blank" database. You could then also
enhance it to say only run this in idle time etc, control various
parameters through the db itself and have it included in the backup.
(OK, you could create a SP that simply fires every hour or whatever,
then have it call other SPs based on rules within the db)
<End Dreamland, back to reality>
Again, it is nothing I can't live without, just a nice to have.
wrote:
> > Is there a scheduler planned for FB, or maintaining this anotherjob
> > for an isql script in the windows scheduler or service sitting onthe
> > server?file,
>
>
> A scheduler is easy! You've already got one!
> crontab entry on Unix/Linux:
>
> # Every hour, run a query
> 0 * * * * /usr/local/scripts/do_something.sh
>
> and in that 'do_something.sh' file, we have:
> /opt/firebird/bin/isql -u sysdba -p masterkey <
> /usr/local/scripts/do_something.sql
>
> And in that 'do_something.sql' (Note the .sql, not the .sh)
> select 'Hello!' from rdb$database;
>
>
> In windows, just use the 'scheduled tasks' system to launch a .bat
> that launches 'isql' with a file full of sql commands.Yeah, that's how I do it now. (isql with -i parameter)
>
> Very easy, and very maintainable.
>
> N
<Begin Dreamland>
It would be nice to have these commands stored in the fdb. I have a
couple of SPs that do some general maintenance. They don't do
anything critical, but if they are not run at some ungodly hour in
the morning, they will run the next time the user uses particular
functions, which slows it down. The reason it is preferable (to me)
is that when we get a new customer, it would be much easier to
preload this schedule in our "blank" database. You could then also
enhance it to say only run this in idle time etc, control various
parameters through the db itself and have it included in the backup.
(OK, you could create a SP that simply fires every hour or whatever,
then have it call other SPs based on rules within the db)
<End Dreamland, back to reality>
Again, it is nothing I can't live without, just a nice to have.