I have written a stored procedure in SQL Server.
Now its just that I don\'t want any one to see my script or edit it.
Please remember that I am working on the a
SQL Server doesn't truly provide a foolproof method to protect module code. The WITH ENCRYPTION
clause should be named something along the lines of WITH LOOSE_OBFUSCATION
, since the "encryption" is very easily thwarted. You're not going to be able to use anything in SQL Server to make the code undecipherable by anyone except the most casual onlookers - anyone determined is going to be able to beat native methods without breaking a sweat.
While this may be good enough for your needs, probably a safer way (but still not perfect) is to put some or all of the procedure's business logic into the CLR (read more here).