Securing my Stored Procedures?
- From: "Jay" <jay6447@xxxxxxxxxxx>
- Date: 26 Nov 2006 22:18:53 -0800
Hi,
I have a database that I have created. Currently, I am the only user of
this database. I connect as 'sa'.
Now, I need to move it to a new Company Server.
The logic in the Stored Procedures in my proprietary and I don't want
any body else to be able to view/edit/delete these existing stored
procedures but be able to execute them. I will now have another
programmer adding new ancillary procedures, create new tables write
front-end programs to call my proprietary procedures etc.
Basically, I don't want any body to be able to view my existing
procedures except me. Is this possible? If so, how do I do this? Once
complete, the database will not have many users - 1 or two, hence, one
'sa' account and one, two other accounts will be more than enough.
Thanks.
.
- Follow-Ups:
- Re: Securing my Stored Procedures?
- From: Chris O'C via SQLMonster.com
- Re: Securing my Stored Procedures?
- Prev by Date: Re: Encrypt/Decrypt SQL Server 2005 data files
- Next by Date: Re: Securing my Stored Procedures?
- Previous by thread: Re: Sql locking other domain account out
- Next by thread: Re: Securing my Stored Procedures?
- Index(es):
Relevant Pages
|
|