Thanks guys. Okay, so there are a few options I can try that rely on the agreement of our brand's strict security policies but one will have to work. Either:

• Create a text file or use the library folder and lock it down to specific users that have SQLServer administrative rights
• Create a local user and password that has access to run the script and has admin rights to SQLServer

The Windows Service option didn't work for me. I use Perl scripted Windows Services on one server with INTSRV but in our store environment they only allow SC.EXE to run and it couldn't get it to accept the path to the Perl.exe program and pass it the path to the script at the same time. It just wouldn't work otherwise I'd have Windows Services running.

Thanks for your help and insights, I have something substantial to work with now :-)