Re: how to secure a sql 2005 database?
- From: Jay B <jayB@xxxxxxxxxxx>
- Date: Fri, 03 Nov 2006 19:10:16 -0500
thanks for the link. that's why i rather keep my stored procedures in my own source code, then pass it thru to sqlexec to execute.
i have greater control of it. executes just as fast.
i'm pretty paranoid about some of my creations, i develop apps to sell, not for clients to take over the database. so i need to protect my rights. its like quickbooks turning over their internal structures, which they really don't, but provide an api to export data out. i will do the same or just provide views for the user to use. that's what ADP does. you never see adp's internal structures.
so are you saying that i can't create a user and make that user the only valid user to get into the database, and unless you know the password, even admins, you cant open the database at all. i would hardcode the pwd in my program of course for it to open the tables.
what do you think?
Jay
Rick Byham, MS wrote:
You can encrypt the stored procedures so even the system administrators cannot see them. See example F at http://msdn2.microsoft.com/en-us/library/ms187926.aspx.
Once encrypted you can't un-encrypt it, so you are responsible for having a backup of the procedure text.
- References:
- how to secure a sql 2005 database?
- From: Jay B
- Re: how to secure a sql 2005 database?
- From: Dejan Sarka
- Re: how to secure a sql 2005 database?
- From: Rick Byham, MS
- how to secure a sql 2005 database?
- Prev by Date: Re: setting up 2005 Developer Edition
- Next by Date: anyone know how to change the name of a view in sql2005?
- Previous by thread: Re: how to secure a sql 2005 database?
- Next by thread: detach replicated databases in sql server 2005
- Index(es):
Relevant Pages
|