Re: How to keep Stored Procedure "a Secret"???

Is it the "text" of the stored proc that you want to keep secret??

If so, how about deleting the contents of the proc from syscomments - it might work, since when the proc is created it's tree is stored in sysprocedures, so I wouldn't think the stuff in syscomments would ever be needed again.

Try it out.....

sp_configure "allow updates",1
go
reconfigure .....
go
use db
go
delete from syscomments where id = object_id("stored_proc_name") go

etc....

Use at your own risk....

Shane

In article <322CD74D.B5D_at_us.oracle.com>, Tim Taylor <ttaylor_at_us.oracle.com> writes:
> Carl Tichler wrote:
> >
> > For what its worth, Oracle has introduced a way to save and load
> > a stored procedure in an encrypted format, as of version 7.1 or 7.2.
> >
> > Carl Tichler
> > catech_at_cloud9.net
> >
> > "hector.tello" <htello_at_onr.com> wrote:
> > >I am looking into migrating an old x-base application to a PowerBuilder with
> > >Sybase/Oracle/MS SQL Server platform. A lot of improvement is expected from moving
> > >the heavy data manipulation procedures to the server as stored procedures. However,
> > >there are a couple of procedures which are proprietary. Not even the customer's DBA

snip....

...
... Received on Wed Sep 04 1996 - 00:00:00 CEST