>
>I cannot agree more with you. Another reason why any self-respecting DBA wouldn't tolerate encrypted SPs is because it would put him out of contol of that part of the SQL Server altogether.

In my situation, users update the database via an application software provided by us. So, the DBA at the customer site still has to rely on the application to maintain the database. We as the software provider are responsible for the source code.

Given that "with encryption" provides no protection at all. The question still remains: How can I protect my source code?