Page 2 of 2

Posted: Thu May 17, 2007 2:53 pm
by regX
I knew you were going to ask me that. :)

I use plain ole SQL statements in my dev simply to define what it is I am looking for in the DB. Sometimes this changes, and I find it more expedient to edit plain text than ask the senior analyst to modify a stored proc.

And get this: I have to submit SQL statements in order to get a stored proc created on the DB server.

I can't disclose what DB server we use per our "Company Privacy Policy". I probably *could* as it really has no impact whatsoever on my companies security, but just in case the Admin is looking....you get the idea.

I can say what it is not: Oracle, Informix, MySQL, Postgres, or MSSQL. Don't guess...you know what it is already...it's not like there are a lot of "Enterprise" database servers around. ;)

Posted: Thu May 17, 2007 3:25 pm
by RobertGonzalez
That doesn't leave a whole bunch of ideas left (but I think I know, and if it is what I think it is, then I would say that you are in the exact same boat as me).

Anyway, in my last project (actually in all of them) the DBA writes the procs that I ask her to write. I tell her what I need and she gives me the return sets according to my request. My user of the app (the user that connects to the DB for the web app) literally has no access to the database server except to use those procs.