I am starting a project that involves moving, reconfiguring and combining several different queues in an already existing system. The system is using a custom Windows service to receive messages and add them to a SQL Server DB. I am just getting started on the project and don't have any specific criticisms of the custom receiver service - but it pre-dates the introduction of triggers and rules. So should I consider extracting the db code from this service and package into an exe by itself and then used the built in trigger functionality to fire the exe instead of maintaining my own service?
It looks attractive because it would be less custom code and allow me to focus on what's important for us (the data - not the communication). But even though it looks good on paper, I'm wondering if there is any field experience that says otherwise.