Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pkuchaliya
Starting Member
49 Posts |
 Posted - 2008-07-10 : 00:09:47
|
Hi to all,I have designed the stored procedure in sql server 2005,I want to make it secured mean it will lock.i lock this but not unable to modify it.Please help me pankaj |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2008-07-10 : 00:19:05
|
see the BOL on CREATE PROCEDURE http://msdn.microsoft.com/en-us/library/ms187926.aspxquote:
ENCRYPTION Indicates that SQL Server will convert the original text of the CREATE PROCEDURE statement to an obfuscated format. The output of the obfuscation is not directly visible in any of the catalog views in SQL Server 2005. Users that have no access to system tables or database files cannot retrieve the obfuscated text. However, the text will be available to privileged users that can either access system tables over the DAC port or directly access database files. Also, users that can attach a debugger to the server process can retrieve the decrypted procedure from memory at runtime. For more information about accessing system metadata, see Metadata Visibility Configuration. This option is not valid for CLR stored procedures. Procedures created by using this option cannot be published as part of SQL Server replication.
KH[spoiler]Time is always against us[/spoiler] |
 |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2008-07-10 : 01:53:08
|
| If you mean , once you've written the procedure , you don't want it altered , you can control up to a certain extent via SecurityJack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
|
|
|
|
|
|
Sql Stored Procedure 2005