March 9, 2009 at 2:30 am
In SQL 7, I used to follow the following steps.
1. CREATE PROCEDURE usr_test ... WITH ENCRYPTION ...
2. After create, generate the CREATE script for this procedure.
I used to get an encrypted string in the script.
3. It was possible to use this encrypted script at my client's place to CREATE and EXECUTE the encrypted procedure.
Now while using SQL 2000, I am not able to generate the CREATE script for encrypted procedures.
What is the solution for this situation?
I don't want my client to view or modify my procedures as I send these Scripts by email attachements.
Thanks.
March 13, 2009 at 2:56 pm
The encryption is done by the compiler. I'm not sure you can stick the encrypted text in there.
It's moot. If you have a client that wants to mess with the T-SQL and is capable of it, they can download a decryption routine in a few minutes from Google. You're wasting time and cycles worrying about this. Tons of vendors build applications on SQL, support them, sell them, etc. with the stored procedure code visible.
March 14, 2009 at 4:49 am
Thanks Steve for your inputs.
The encrypted string of the Create Procedure code generated by SQL 7 can also be used to create procedure in versions later than SQL 7.
I agree with you that I should stop worrying and if at all need be I may write an application to create the procedures.
Thanks again.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply