Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Job / Task Scheduler [CORE743] #1118

Open
firebird-automations opened this issue Mar 6, 2006 · 11 comments
Open

Job / Task Scheduler [CORE743] #1118

firebird-automations opened this issue Mar 6, 2006 · 11 comments

Comments

@firebird-automations
Copy link
Collaborator

firebird-automations commented Mar 6, 2006

Submitted by: tectsoft (tectsoft)

Relate to CORE1613
Is duplicated by CORE2148
Is duplicated by CORE3193
Is duplicated by CORE4012
Relate to CORE2021
Is duplicated by CORE1717

Votes: 34

SFID: 1444172#⁠
Submitted By: tectsoft

It would be nice if DBA's or DB Owners had the ability
to create/ammend/delete a scheduled task or job for
each database (or server wide).

Including:

#⁠ Initiate a task as soon as the engine is started.
#⁠ Initiate a task during idle CPU time.
#⁠ Create a one off task for execution on a specified
date/time.
#⁠ Create Recurring tasks.
#⁠ Initiate a task when a user connects/disconnects
from a database.
#⁠ Ability to disable/enable tasks.
#⁠ Ability to backup a database.

This is a follow on from this proposal on architect
list
(http://groups.yahoo.com/group/Firebird-Architect/message/8304 (archive))

rgds

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Component: Engine [ 10000 ]

assignee: Dmitry Yemanov [ dimitr ]

SF_ID: 1444172 =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

assignee: Dmitry Yemanov [ dimitr ] =>

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Workflow: jira [ 10767 ] => Firebird [ 15171 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue relate to CORE1613 [ CORE1613 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

Link: This issue is duplicated by CORE2148 [ CORE2148 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue is duplicated by CORE3193 [ CORE3193 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue is duplicated by CORE4012 [ CORE4012 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Sean Leyne (seanleyne)

The implementation of this feature would require a complex infrastructure (i.e. Server/Database manager) which would a list of registered databases, which be responsible for ensuring that the databases are opened/active on a 24 hour basis. The functionality could then also include features like server health monitoring, health dashboard and/or email notifications.

This would add complexity to the current install/deployment process, which may not be required for all installations.

This should be taken up as a separate module (like Guardian), it should not be considered part of the engine itself.

@firebird-automations
Copy link
Collaborator Author

Modified by: Sean Leyne (seanleyne)

Link: This issue relate to CORE2021 [ CORE2021 ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

Link: This issue is duplicated by CORE1717 [ CORE1717 ]

@firebird-automations
Copy link
Collaborator Author

Commented by: TIP Group, S.A. (Olivier Mascia) (tipgroup)

Sounds like database and application servers confusion to me.
Couldn't FB3 plugin architecture be a simple host for such add-on features?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant