Skip to main content

Encrypt all Stored Proceedure ...

There are situations where we would have written lots of stored procedure for a project. If at all we want to encrypt all the SPs at one shot, as of now we don't have any build-in function or tool to do that. The below SP does that with the help of "Cursor".

This SP is intelligent (!!) enough to encrypt all Stored procs within the current database except itself.

There is no "easy" way to decrypt the encrypted procedures. So it is always advisable to generate scripts of ALL SPs before executing the below piece of code. Also this code snippet would only work for those SPs whose content are within 8000 characters.

Create procedure uspEncryptAllSP
As
Declare @procName varchar(255),
@procContent varchar(8000),
@sqlQuery varchar(8000)

Set nocount on

Declare curEncrypt cursor for
Select
so.name,
sc.text
From
Sysobjects so,
Syscomments sc
Where
sc.id=so.id and
so.type ='p' and
so.category=0 and
so.name <> 'uspEncryptAllSP' and
sc.encrypted=0

Open curEncrypt
Fetch next from curEncrypt into @procName, @procContent

While @@Fetch_Status = 0
Begin

Print 'Encrypting the Stored Procedure: ' + @procName
Execute ('drop procedure ' + @procName)

Set @sqlQuery = Replace(@procContent, 'Create procedure ' + @procName, 'Create procedure ' + @procName + ' With Encryption')
Execute (@sqlQuery)

Fetch next from curEncrypt into @procName, @procContent

End
Close curEncrypt
Deallocate curEncrypt

Print 'Mission Completed !!!'
Go

We can still improve this code by putting the main logic within transaction. So that if at due to some reasons the procedure is deleted but could not be recreated with encryption we could roll back.

Comments

Anonymous said…
Hello,

To remove the 8000 limit could you use varcharmax instead of varchar?

I guess that would only be for SQL Server 2005 and above though
Rich said…
This script will not work with stored procedures which define parameters.
Anonymous said…
This script will not function with stored procedures which define parameters. Replace on ' AS ' with ' with encryption as ' instead.
magnus said…
Dangerous to replace ' AS ' since that can be used in many other places. As in SELECT columnName AS 'otherName'
Unknown said…
This code is not working in procedures having input and ouptut parameters

Popular posts from this blog

[Non Tech] Want to know the recipe for Omelette :)

Fed up with Bread - Jam and Curd Rice, today i wanted to eat Omelette. Interesting part is I wanted to cook it myself :) So in the first picture you see all the items which are needed for preparing an Omelette. When I had a closer look at the eggs I see that almost all the eggs are broken. But believe me when I bought it couple of days back it was in perfect condition! I was wondering whether the eggs have become rotten or pretty old to consume! I tried taking an egg and break it but couldn't break it at all :) Since I have kept in the freezer all the eggs have frozen and looked like a iron ball :) After trying for few minutes of trying i removed the shell of the egg and then kept that iron ball :) into a bowl and placed it within Oven. I heated it for 1 minute and checked. It melted only to a limit. So i just set it for another 2 minutes and checked it later. It has melted but the part of the egg white has become a Omelette :( I didn't leave it there. I took the bowl out of ...

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul...

My Wedding Anniversary :)

Six years back on the same day I married Sai Lakshmi (12-July-2000). I know Sai for almost 13 years now :) I fell in love with her during my 12th standard. I know @ 17 yrs any person wouldn't be matured enough to make a big decision like this. But thank God my choice was perfect :) Even now, very often we used to think about the past and laugh at our behaviors/actions then. My love story would be really interesting (at least for me and Sai :)) and I am sure none of you guys would be interested in reading about it so lemme not get into it in-depth. But one thing which I want to share is "Without Sai, I wouldn't have entered into the IT field at all". She was instrumental in convincing me to study my Master's degree in Computer Application. That's the move that changed my career. Till my schooling, my dream was to either become a "big" sportsman (Cricket and Badminton were my favorites at that time.) or an Aeronautics engineer. Unfortunately, my l...