Stored procs vs. direct SQL, password confidentiality
Posted: Thu 07 Sep 2006 09:28
Hi,
Do you see any argument in favor or against usage of a stored procedure vs. direct SQL in code with CoreLab library?
Performance?
Database user confidentiality (db user is only authorized to call stored procs, etc.) ?
My boss is very paranoiac about db user password confidentiality. Has someone already implemented a way to have the username/pwd fields encrypted in an external config file and decrypted in code to be used to connect to a DB?
Thanks.
Adriano Labate
Do you see any argument in favor or against usage of a stored procedure vs. direct SQL in code with CoreLab library?
Performance?
Database user confidentiality (db user is only authorized to call stored procs, etc.) ?
My boss is very paranoiac about db user password confidentiality. Has someone already implemented a way to have the username/pwd fields encrypted in an external config file and decrypted in code to be used to connect to a DB?
Thanks.
Adriano Labate