Yes, you can use the WITH ENCRYPTION setting when you create the
procedure and view.  However the encryption algorithm being used is
well known, and it's very easy to reverse engineer the procedure/view
code.

Denny

You can create a procedure with encryption, it is not 100% effective but it
will keep out the casual person.

In SQL Server 2005 you can leverage the CLR and have some of your logic in
assemblies.  Not necessarily the best for performance, but you will have to
decide that trade-off for yourself.

Better yet is to not give such rights to users you don't trust.  :-)

On 7/17/08 3:45 PM, in article
050257D4-5170-4BCA-953F-CBEE29E4EDA3@microsoft.com, "Dan Shepherd"
<DanShepherd@discussions.microsoft.com> wrote:

Well, what type of user?
In SQL Server 2000, by default, a user cannot alter a database object,
unless you add them to the sysadmin or DBO role, but they can still view the
schema using sp_helptext. In SQL Server 2005, a user by default cannot view
schema either unless you grant them ownership or VIEW DEFINITION permission,
etc.
Ideally, you should grant application users (as opposed to developers or
power users) only exec permission to those specific stored procedures they
need access to so they don't have the liberty of perusing objects the
database.