> However one of our developers has expressed concern as the > applications are reliant on SQL Server and he regards any > application that is not self reliant as a poor candidate for a > service.
not sure what "reliant" means here exactly - you mean the service is accessing some SQL database? why is that a problem? the requirement that anything running as a Win32 service be "self-reliant" is is pretty limiting. Every service needs to be able to deal with failures - sometimes the resources it needs aren't available - sometimes things go wrong. IMHO there is nothing particularly special about MSSQL in this regard - it's just another resource like WINSOCK or RAS or an Exchange server. > I would appreciate comments on limitations or experiences with > services which are reliant on database services. in general i think there is one thing that every non-trivial service should have designed in from the start - LOGGING. ideally it should be possible to turn it on and off using the NT SCM without shutting down the service. And also possible to switch between VERBOSE and normal logging levels. but however you do it - being able to analyse the history of some wierd failure - particularly if multiple threads are executing- is worth the extra development burdon of implementing the logging mechanism. FWIW -ns http://www.roserox.co.th --------------------------------------------------------------------------- New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe offtopic" Web Archive at: http://www.mail-archive.com/offtopic%40delphi.org.nz/
