Running Batch Jobs without Exposing User ID/Passwords or Source of SQL statements?!

Hi.

I have a number of batch jobs that are ran nightly on our Windows 2000 based Oracle 8.1.7 (soon to be 9i) server. I have these designed just right, so the Windows Scheduled Tasks runs them and then a parser goes through the output and, in case of errors, sends me a page...

The database is our financial system which requires users to login using Oracle based user ID / Password.

Here are two concerns:

1. Right now, the batch files used to schedule the processes, parse the output and generate Emails, have a set of Oracle User ID/Password hardcoded in them. Ideally, I would want to use Windows authentication to schedule the jobs so that passwords are not visible to others.
2. Of course, the source of the batch process is visible in SQL format and can be viewed and, worse yet, modified by malicious hackers... Ideally, I guess, most of the SQL processing could move to stored procedures...

Dare I mention SQLServer 2000?! I had to recently pick that up to help manage several other projects and am quite impressed by the way one creates Jobs and processes that remain pretty much secure from these kind of issues. I know Oracle must have similar features, but I am not familiar enough with them and hope you can make appropriate suggestions... How do others approach these problems?

Thanks. Received on Sat Jul 03 2004 - 21:29:17 CDT