February 12, 2008 at 11:10 am
I haven't implemented this yet in production, I wanted to send it up the flag pole and see who shoots at it. 😀
I did a little experimenting a while back to see if I could hide my source code for views (it should work the same for sprocs) by denying select on syscomments. It seems to work just fine, and I don't have the mess of dealing with encrypted code.
Have I missed any potential problems here? Comments?
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 12, 2008 at 1:27 pm
It works.
We can prevent non-sa users from viewing the codes. On the other hand, we have to set DENY to each individual user/group.
Do I interprete your intention correctly?
February 12, 2008 at 1:58 pm
From a strict standpoint, there are ways around denying select rights that would not work on encryption, such as copying actual files and viewing them elsewhere. But from a practical standpoint, it will probably accomplish what you need.
---
Timothy A Wiseman
SQL Blog: http://timothyawiseman.wordpress.com/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply