Arthur Fuller
fuller.artful at gmail.com
Wed Jun 11 05:56:26 CDT 2008
Thanks for the input, Stuart. Currently I'm thinking that I should try what I need using SSIS (small footprint, external process), but I'm still open on the subject. Arthur On Tue, Jun 10, 2008 at 7:40 PM, Stuart McLachlan <stuart at lexacorp.com.pg> wrote: > Triggers are probably out of the question because you need to process the > rows > sequentially. > > Procs with Infinite loops tend to be resource hogs and it's not so easy to > program complex > business logic in TSQL. > > I'd go with an external agent. > > I've got a couple of similar things running. Both use ODBC for the > connection and a front > end application or service which sits in the background and periodically > polls the data base, > applies the logic and updates where required. > > I generally write this sort of thing in PowerBasic with the SQL Tools ODBC > package but any > environment which can generate small footprint executables, can access > ODBC, can > "sleep" and can spawn threads will do it. > >