From: Alex P. <pes...@ma...> - 2014-04-29 13:57:06
|
On 04/29/14 16:46, Daniel Rail wrote: > Hi, > > At April 29, 2014, 5:09 AM, Mark Rotteveel wrote: > >> On Tue, 29 Apr 2014 11:58:57 +0400, Dmitry Yemanov <fir...@ya...> >> wrote: >>> Who should initiate that dedicated listener deamon/user after a server >>> restart? Should the server attach all the databases itself to check >>> whether one needs a startup? What about databases unknown to the server >>> (not present in databases.conf)? >> If you look at SQL Server, there jobs themselves are not defined for a >> specific database (although they may depend on one or more databases). >> AFAIK they are stored in the master database. Execution requires an Agent >> service to be running. > And, even with the MS-SQL Agent service, it is no guarantee. We tried > setting up maintenance plans in MS-SQL 2012, and for some reason, the > maintenance plan file/record gets corrupted and will not work anymore, > and is no longer modifiable(and this is after creating multiple > maintenance plans, even after a full reinstall). So, we simply decided > to create a PowerShell script that will execute the maintenance tasks > and use the Windows Task Scheduler to schedule when the script will > run. > > So, for Firebird, I think that it would be up to the user and/or the > software developer to decide how they would want to execute such > tasks(either creating their own service, or using a batch/script to > execute the commands scheduled via a task scheduler). As an example, > our application has a service(for an n-tier application) that runs on > the server, and we simply add the maintenance tasks in it, and > they are scheduled when they are to be executed. > > So, for me, it is not something that I see as a priority for Firebird. > Since there is always another way of doing it. +1 I also do not see big need in a feature that can be easily replaced with std OS tools. |