Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
clubhi
Starting Member
4 Posts |
 Posted - 2006-10-17 : 10:59:18
|
| My manager wants some complex event system where we can monitor anything in the database,such as a if we decide we want to get updated if a certain column gets changed, or if a row has not been inserted into a table in the last 5 minutes.He wants it completly generic so that we can build on it later.Is something like this really worth investing time into? It seems like their would be a lot of stuff out their that does this already. I myself would have no problem writeing an app to do all this with a help of a few triggers. But he wants it almost all inside the database. Lots of of stored procedures,lots of triggers, SQL conditions that decide if things should execute...what do you guys think? |
|
|
snSQL
Master Smack Fu Yak Hacker
1837 Posts |
Posted - 2006-10-17 : 11:51:36
|
quote:
I myself would have no problem writeing an app to do all this with a help of a few triggers. But he wants it almost all inside the database.
Well triggers and stored procedures are inside the database so what is the question? |
 |
|
|
madhivanan
Premature Yak Congratulator
22864 Posts |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-10-18 : 15:01:01
|
quote:
Originally posted by clubhi
My manager wants some complex event system where we can monitor anything in the database,such as a if we decide we want to get updated if a certain column gets changed, or if a row has not been inserted into a table in the last 5 minutes.He wants it completly generic so that we can build on it later.Is something like this really worth investing time into? It seems like their would be a lot of stuff out their that does this already. I myself would have no problem writeing an app to do all this with a help of a few triggers. But he wants it almost all inside the database. Lots of of stored procedures,lots of triggers, SQL conditions that decide if things should execute...what do you guys think?
I would ask your manager to explain in detail the design he has for how to do this. Truthfully, it sounds like he doesn't really know what he's talking about. A database isn't an event engine, it's a system for storing and maintaining data, and processing transactions.CODO ERGO SUM |
|
|
|
|
|
|
event system