Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Register Now and get your question answered!
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 How to decrypt encrypted code ?
 Topic Locked
 Printer Friendly
Author Previous Topic Topic Next Topic  

Starting Member

22 Posts

Posted - 05/15/2002 :  00:08:04  Show Profile
Then how to decrypt encrypted code.... could someone teach me ???

Most Valuable Yak

15732 Posts

Posted - 05/15/2002 :  00:25:54  Show Profile  Visit robvolk's Homepage
OK, I'm gonna go on a rant here, because quite frankly this needs to be said...

If anyone is curious about, or considering, or thinking about encrypting stored procedures in SQL Server


Here's why:

-Sooner or later, mostly sooner, you're gonna encrypt something and not have a plaintext copy of the code. You know what that means? You're FUCKED, SOL, SCREWED.

-For those who will say, "Yeah, well I can get something off the internet that can decrypt them!"...GREAT, THEN WHAT'S THE POINT OF ENCRYPTING IT? Like you're the ONLY person who would use that decrypt procedure!

The thing is this: UNLESS you are in a highly organized, disciplined, team environment, with anal retentive coding procedures and multiple levels of code review, full source control (Source Safe) and fully documented code revision history tracking, you are not at a professional-enough level to consider encryption. This is not intended as an insult to anyone's knowledge or coding ability.

Encrypting source code is ONLY effective in that kind of environment, because there are multiple safeguards to prevent code loss like you're experiencing here. People who have attained this level of discipline and professionalism NEVER ask how to decrypt a procedure, because they will NEVER accidentally encrypt one.

This is a nasty slap on the wrist, and frankly, you should take it as a learning experience. There have been FAR TOO MANY posts about how to decrypt a procedure, and it has to stop. The best way for it to stop: DON'T ENCRYPT YOUR PROCEDURES. Say that to yourself over and over and over again as you rewrite all of the code you lost.

No, we are not gonna help you decrypt the procedures. Period. Either rewrite your code, or move on to another web site.

Go to Top of Page

Chief SQLTeam Crack Dealer

4149 Posts

Posted - 05/15/2002 :  00:29:03  Show Profile  Visit graz's Homepage
Quite a hum-dinger of a post for number 3,900. I'm quivering in fear that I may feel the rage of number 4,000 :)

I'm opposed to encryption also. It's especially difficult to support vendor packages when they encrypt their procedures. Especially difficult.

Creating tomorrow's legacy systems today.
One crisis at a time.
Go to Top of Page
  Previous Topic Topic Next Topic  
 Topic Locked
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000