The agent that sits on the database server is responsible for two things:
- Query the database to identify when various trigger conditions are met
- When a trigger condition is met, extract another piece of data from the database and send to the "Web App" server for processing
Theoretically, the entire agent is unescessary...I could use remote DB access credentials to perform the same task. I assumed most companies don't like giving out remote-access credentials though, and decided a local agent that reports home is a better option.
So a plugin to the database is unnecessary since a local DB connection would be sufficient, but I think the rest of what you said is exactly what I'll end up doing.
- Query the database to identify when various trigger conditions are met
- When a trigger condition is met, extract another piece of data from the database and send to the "Web App" server for processing
Theoretically, the entire agent is unescessary...I could use remote DB access credentials to perform the same task. I assumed most companies don't like giving out remote-access credentials though, and decided a local agent that reports home is a better option.
So a plugin to the database is unnecessary since a local DB connection would be sufficient, but I think the rest of what you said is exactly what I'll end up doing.