Encrypt Stored Procedure

Question

Post reply

Encrypt Stored Procedure

JuanBob

SSCertifiable

Points: 5059
More actions
September 23, 2005 at 2:23 pm

#89072

I have built a stored procedure that I would like to encrypt.

Are there other alternatives, or what are the options?

Can it be converted to a dll?

Maybe I'm out of my mind!

Thanks!

Viewing 11 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic. Login to reply

noeld SSC Guru Points: 96590 More actions · Answer 1

noeld

SSC Guru

Points: 96590

September 23, 2005 at 2:27 pm

#592775

You can use WITH ENCRIPTION on the procedure declaration, you can create an exteded stored procedure using C++, you can create COM Component and use sp_OA* calls but the real question is: why do you want that?

* Noel

JuanBob SSCertifiable Points: 5059 More actions · Answer 2

Thanks for the multiple suggestions!

There are two reasons.

First and Foremost, Security: I've built some very useful SP's that analyze certain aspects of the CRM system. The clients also have inhouse users with access to SQL. I cannot control their security as this is defined by them. I have experience with client employees messing with stuff I built and I take the heat for things breaking.

Resell: There are other legal obligations not to discuss here, but I want to deploy this to other clients. However, I do not want competitors taking my code if at all possible.

Thanks again!!

Ninja's_RGR'us SSC Guru Points: 294069 More actions · Answer 3

Ninja's_RGR'us

SSC Guru

Points: 294069

September 23, 2005 at 2:49 pm

#592786

Just go with the with encryption.

Make sure that you have backups of the code cause you won't be able to access it again.

However I must tell you that there are some working de-encrypters that work, so they might find out anyways.

noeld SSC Guru Points: 96590 More actions · Answer 4

noeld

SSC Guru

Points: 96590

September 23, 2005 at 2:56 pm

#592789

Like explained above "with encryption" is the easiest and more portable but it can be decripted. If you really need protection only extended stored procedures will help you ("a bit") in keeping IP. The other way is to put the core logic in the application but don't know really the details!

Good luck

* Noel

David.Poole SSC Guru Points: 75656 More actions · Answer 5

OK encrypt your procs but make sure that you have scripts should you need to get hold of them. Frankly it is more trouble than it is worth.

I wouldn't worry too much about people stealing you procs. Without the database schema and a intimate knowledge of your app they are not much use.

If you are worried about customers ruining your app by fiddling where they shouldn't then as part of the support provision you should have the facility to request a backup of their database.

Again, when I was working with CMS systems the better vendors would request detailed platform information plus a list of steps that would reproduce the error or that were taken to get the error.

One question they would ask was "can you reproduce the error in your environment"? If an error cannot be reproduced then it could easily be user error rather than a system fault. However, if the error can be reproduced in their environment but not yours it could indicate that they have been meddling.

If you can get a backup of their system then there are tools out there to compare the databases are report on the differences.

LinkedIn Profile

JuanBob SSCertifiable Points: 5059 More actions · Answer 6

Thank you all for the replies. All very understandable and appreciated!

Quick question: If I wanted to create an Extended SP, it sounds like I need Visual Studio or equivalent. Does it require knowledge of C++ language, or is there a very understandable wizard that is available? I'm a novice T-SQL user who can get things done, but never touched C anything.

TIA