Encryption

[gussifinknottle]

To expand on the last thread I posted. I send out Patch Scripts that have fixes between Maintenance releases. But I don't want the customers seeing what I have in the patch. If it is a normal stored procedure, I use 'WITH ENCRYPTION' option. I would like to use something similar. (Sort of like an .exe, which the customers would run.)

 

[TomSark]

That's going to be difficult, because if you are sending embedded SQL to SQL Server, you will be able to see the executing code in Profiler.

One way would be to create encrypted procs and run those. You could send CREATE PROC...WITH ENCRYPTION statements from a VB program, then turn around and run them from the VB Program, then Drop them when you are done...

Or.. you could code a SQL-NS application that does this, so that they can't see what you are doing... just some thoughts... Tom Davis
tdavis@sark.com

http://www.sarkdallas.com